- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IError 1 error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3) Link
I'm compiling in debug mode,NO optimization, 32-bit target. It does not occur in release mode, nor in 64-bit mode. The only difference was I turned on gen-interface for diagnostics, then turned it back off again after making corrections. I cleaned the debug solution, still get the same problem; I then deleted everything in the debug directory and still get the same problem.
I have not tried a rebuild with the other configurations, but I'm loath to do so in case the problem crops up there as well (the build for these others is fine after the corrections made).
What can I do to eliminate this?
Thanks,
Neal
I'm compiling in debug mode,NO optimization, 32-bit target. It does not occur in release mode, nor in 64-bit mode. The only difference was I turned on gen-interface for diagnostics, then turned it back off again after making corrections. I cleaned the debug solution, still get the same problem; I then deleted everything in the debug directory and still get the same problem.
I have not tried a rebuild with the other configurations, but I'm loath to do so in case the problem crops up there as well (the build for these others is fine after the corrections made).
What can I do to eliminate this?
Thanks,
Neal
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - nvaneck
IError 1 error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3) Link
I'm compiling in debug mode,NO optimization, 32-bit target. It does not occur in release mode, nor in 64-bit mode. The only difference was I turned on gen-interface for diagnostics, then turned it back off again after making corrections. I cleaned the debug solution, still get the same problem; I then deleted everything in the debug directory and still get the same problem.
I have not tried a rebuild with the other configurations, but I'm loath to do so in case the problem crops up there as well (the build for these others is fine after the corrections made).
What can I do to eliminate this?
Thanks,
Neal
I'm compiling in debug mode,NO optimization, 32-bit target. It does not occur in release mode, nor in 64-bit mode. The only difference was I turned on gen-interface for diagnostics, then turned it back off again after making corrections. I cleaned the debug solution, still get the same problem; I then deleted everything in the debug directory and still get the same problem.
I have not tried a rebuild with the other configurations, but I'm loath to do so in case the problem crops up there as well (the build for these others is fine after the corrections made).
What can I do to eliminate this?
Thanks,
Neal
Actaully, a further message flips off the screen before the one above; it's an internal compiler error.
It comes up during the link ste, preceded by 101004_3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not much we can do with this little information, other than to advise you to submit the reproducer on your account on premier.intel.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
Not much we can do with this little information, other than to advise you to submit the reproducer on your account on premier.intel.com
Not a problem; I've discovered it is due to the option "analyze include files" which I somehow had switched on. Turning it off solves the problem for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please do provide us with a test case so that we can fix the bug. You can attach it here or use Intel Premier Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Please do provide us with a test case so that we can fix the bug. You can attach it here or use Intel Premier Support.
Here's one:
CHARACTER C_REC*1024
I=INDEX(C_REC(1:LEN_STAMP),'STAMP2.BMP')
END
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. What compiler options are you using? Your reference to "analyze include files" makes me think you are using Source Checker (formerly Static Verifier.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Thanks. What compiler options are you using? Your reference to "analyze include files" makes me think you are using Source Checker (formerly Static Verifier.)
No, for this test,just standard options when you start a new project, then check that option underdiagnostics in a debug configuration. Makes no sense with static verification "none", but I wasn't intending to use static verification....
Using version 10.1
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