We are using VS 2005 + Intel 9.1.034 compilers on a large project with multiple win32 and x64 configurations, and frankly, it has become a nightmare. Here is a laundry list of issues with this (admittedly) complex C++/MFC project
- Visual Studio crashes repeatedly ( 10 times a day). This happens on all three development machines ( XP, 2G RAM). Every time we exit Studio it crashes now (SP1). Only with this project.
- Visual Studio crashes repeatedly in 'batch mode'
Since you cannot batch build a intel C++ visual studio project using vcbuild, you have to use "devenv" to batch build. Our nightly builds crash every night now.
- Source code control integration seems to get confused by the .icproj/.vcproj dichotomy. We have completely disabled all source code control integration and use SourceSafe as a separate application.
- Read-only .icproj files get modified ( and the settings get confused) by the Intel VS Integration tool. This is somewhat random, but it is hugely frustrating, as you open a project, build, and find that the build fails. The offending project will now have a writable and modified .icproj which needs to be manually replaced by the version in source control. No warning is given, the READ-ONLY file just gets changed.
- When building the projects , randomly some C++ .obj files will be created by the Intel Compiler with 0 bytes size, and then the link phase will fail with "multi-file optimization error". One needs to either restart the build or manually recompile single files. This completly breaks our automated build.
- The FIASCO with SP1 and the fatal link errrors with any code compiled with Intel Compilers and /Zi. 034 still has not fixed the problem totally, we now get "debugging information corrupt" in debug builds
I have submitted all these issues to Premier Support, but of course, the issue gets stuck in "waiting for customer" as they cannot reproduce the problems unless I send 2G of project/proprietary source files...