Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29250 Discussions

Unresolved external error with EQUIVALENCE statement

Dishaw__Jim
Beginner
509 Views
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 /Qparallel
I get an functioning program. When I compile with
/nopdbfile /Od /debug:full /check:all /traceback
I 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?

0 Kudos
2 Replies
Steven_L_Intel1
Employee
509 Views

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?

0 Kudos
Dishaw__Jim
Beginner
509 Views
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.
0 Kudos
Reply