- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Tags:
- CC++
- Development Tools
- Intel® C++ Compiler
- Intel® Parallel Studio XE
- Intel® System Studio
- Optimization
- Parallel Computing
- Vectorization
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Marc,
I looked up in our database, and didn't find anything similar to the error message you observed. Could you please provide a small test case, so that I can reproduce the error on my machine?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems that some option broke the 14.0 compiler. Please open "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\PlatformToolsets\Intel C++ Compiler XE 14.0\Microsoft.Cpp.x64.Intel C++ Compiler XE 14.0.targets", and see what is in line 306. It's likely that that line caused the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Marc,
I'm sending you a private message. Please send me your "Microsoft.Cpp.x64.Intel C++ Compiler XE 14.0.targets" file to my email box.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just in case any one else who ran into this issue (14.0.targets(306,5): error : Element has an invalid value of "false") too. Marc confirmed that replacing his 14.0.targets file with mine solves the problem. I'm attaching mine here. Not clear what caused the problem yet.
Instructions: Quit VS IDE. Backup your targets file C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\PlatformToolsets\Intel C++ Compiler XE 14.0\Microsoft.Cpp.x64.Intel C++ Compiler XE 14.0.targets. Then replace it with my targets file. And then restart VS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got this error as well using vs2013 with Intel 16.0 and linking with a fresh boost 1_61 build.
The solution for me was to turn-off multi-file optimization. Interprocedural Optimization No in the IDE.
Hope this helps someone.
Andrew.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Andrew R. wrote:
I got this error as well using vs2013 with Intel 16.0 and linking with a fresh boost 1_61 build.
The solution for me was to turn-off multi-file optimization. Interprocedural Optimization No in the IDE.
Hope this helps someone.
Andrew.
Hi Andrew,
Is the error you observed exactly same as what Marc saw (error : 010101_45097)? If the error is reproducible with 16.0 update 3 compiler, please upload a small test case for me. I'd love to look into it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Andrew,
I recently installed Intel Parallel Studio 16.0 (with update 3). I am using this with Microsoft Visual Studio 2015 (update 2). I have a project that I have been working on that builds with no errors in release mode. However, when I switched to debug mode I got the following error...
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime_exception.h(82) (col. 13): : error : 010101_45097
xilink: : error #10014: problem during multi-file optimization compilation (code 4)
xilink: : error #10014: problem during multi-file optimization compilation (code 4)
I checked the property pages for my project in Visual Studio and the Interprocedural Optimization option was set to No in the C/C++ --> Optimization [Intel] section. However, the Interprocedural Optimization option under the Linker settings was set to Yes. After switching this to No, my project built with no errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have encountered the same error code, Intel C++ Compiler 17.0 (2017.4.210), building in release mode, with various optimisations enabled.
The line on which the error was reported was a trivial access function, returning a char* - an unlikely culprit for anything pernicious.
Doug's suggestion of disabling interprocedural optimisations allowed the build to complete. Thanks Doug.
(I do have less confidence in it than I might, however, with an undocumented error being emitted for unknown reasons.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
it seems like a bug again. this type of bugs is not easy to reproduce. in case you have a reproducer, could you report & share it to Intel Online service center?
thank you very much,
Jennifer
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page