- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a code that uses EQUIVALENCE statements. When I compile with the following options
/nodebug /check:none /G7 /O2 /Og /QaxN /QxK /Qglobal-hoist /Qip /Qopenmp /QparallelI get an functioning program. When I compile with
/nopdbfile /Od /debug:full /check:all /tracebackI get errors during linking that there are unresolved externals. When I look up the unresolved symbols, they are all attributable to an EQUIVALENCE statement.
Changing the code to remove the EQUIVALENCE statement is not an option for a variety of reason. Any ideas on the cause of the problem and how to rectify it?
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sounds like a compiler bug, though without seeing a test case I can't tell for sure. Please report it and attach a test case to Intel Premier Support.
Does removing the /debug make the error go away?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I change the /debug:full to /debug:minimal (or eliminate the /debug:full entirely) the problem goes away. As for a test case--that is going to be very tricky. I'll have to make an equivalent version--I don't have the authority to redistribute the code.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page