If this failure comes up as the first indication of error in a clean rebuild, it looks like a bug. I can think only of submitting a problem report with the test case (at least the files required to link), or cutting back on IPO if you have that option set in all or part of your project. There's advice on applying IPO to large projects in the documentation in the compiler installation. You may find that IPO isn't contributing much.
Neither IPO or the MSVC equivalent (/GL) can be used in a project which combines objects which you build by both Intel and Microsoft compilers.
Hi Tim, I have tried a couple of things and but no luck. All my tries are complete rebuilds.
1. turned off all optimizations
2. like 1. and compiler symbols like _SECURE_SCL=0 and _HAS_ITERATOR_DEBUGGING=0
3. like 1. and 2. and explicitly turning off Whole Program Optimization
I'm not sure if I can create a test case which would recreate this problem. The project I'm compiling is fairly big and proprietary code. Is there maybe a log file or core dump that I could send in?
Also, where can I retrieve the actual command line that invokes xilink?