- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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
링크가 복사됨
7 응답
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Thanks. What compiler options are you using? Your reference to "analyze include files" makes me think you are using Source Checker (formerly Static Verifier.)
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
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