Unwanted recompiles using C++ compiler 2013 on MSVS 2012

Unwanted recompiles using C++ compiler 2013 on MSVS 2012

Hello!

I'm using Intel C++ Composer XE 2013 (w_ccompxe_2013.1.119) on MS Visual Studio 2012 (11.0.51106.01). I build my solution in x64 and Win32. I have a 8 core computer and allow parallel compiling (/MP).

The problem that occurs is the following: when I modify a single file (.cpp) in a project, almost all other .cpp files are recompiled. They should not since no dependencies have been modified. Only the modified file must be recompiled.

We tried the same build using the Microsoft compiler and this problem doesn't occur. It seems linked to the Intel compiler.

Any idea how to fix this bug and to avoid such a waste of time? Feel free to request more specific info.

Thanks in advance for your help!

Dominique B.

33 post / 0 nuovi
Ultimo contenuto
Per informazioni complete sulle ottimizzazioni del compilatore, consultare l'Avviso sull'ottimizzazione

Hi,
Could you please see if the same issue exists even when you disable /MP switch. If yes please do let me know. However it would be great if you can provide me an testcase to reproduce an issue.

Regards,
Sukruth H V

Hi sukruth,

The problem doesn't occur when I disable /MP. However, once /MP is disabled, the problem occurs the first time I rebuild but not the next times. This could lead to a bug due to (intermediate) files generated during the previous build before I switched /MP to NO.

I send you my solution. It is in the file "TestForIntel_1.zip" and contains all the .h, .cpp, .vcxproj, .vcxproj.filters and .sln files.

Regards,
Dominique

Allegati: 

AllegatoDimensione
Download testforintel-1.zip11.49 KB

Hi Dominique,

Could you try to use Precompiled Headers? I see that you don't use that feature in your test project.

Best regards,
Sergey

Hi Sergey,
I added a precompiled header (that is, pch.h, pch.cpp then added pch.h to all .cpp). I switched to "Use Precompiled Header" but for file pch.cpp which is set to "Create Precompiled Header". I observed the same phenomenon.

I send you the modified solution.

Regards,
Dominique

Allegati: 

AllegatoDimensione
Download testforintel-1-with-pch.zip10.27 KB

>>...I added a precompiled header (that is, pch.h, pch.cpp then added pch.h to all .cpp). I switched to "Use Precompiled Header" but
>>for file pch.cpp which is set to "Create Precompiled Header". I observed the same phenomenon.

Thanks, Dominique. There are already a couple of similar reports from different developers who are using Intel C++ compiler. That problem looks very strange, it is easily reproducible and still not fixed.

Some time ago I had a problem with compiling order. That is, if Microsoft C++ compiler compiles source files in order from A to Z, then Intel C++ compiler compiles the same source files in order from Z to A. I wonder if these two problems somehow related.

Sergey,

Does a work around exist?

Notice: I remarked that the compiler looks for the .pchi file when using precompiled headers and this file cannot be found. It is generated when I compile only the pch .cpp file but if a compile another .cpp file, the .pchi file is deleted. Note also that I set the file name to .pch, the "i" at the end has been added by the compiler I guess.

Is it possible that MSBuild is fooled by the extension .pchi rather than being the expected one .pch? This seems not directly linked to the thread but maybe it is.

Thanks.

Hi,
We have submit an tracker to our development team and would update you on this once this has been fixed. Thanks for your testcase.

Regards,
Sukruth H V

>>...Does a work around exist?

It looks like No and it would be already posted. I also see that VS 2010 and VS 2012 ( different Editions ) are less stable compared to VS 2008 ( especially Professional Edition ) and that re-compiling problem could be a result of different issues with MSBuild and Intel C++ compiler. Just search the web with a statement 'MSBuild problem' and you can get about 550,000 results ( in 0.23 seconds ). I hope that it will be fixed soon.

Thanks Sukruth for the update.

Any updates on this issue? I just converted to VS 2012 and every time I hit build (or just "run") it takes 5-10 minutes for VS to rebuild files that were not changed... Productivity is practically zero.

>>...Productivity is practically zero.

Sorry to see that statement.

This is a statement from your 1st post again:

>>... I build my solution in x64 and Win32. I have a 8 core computer and allow parallel compiling (/MP).

Could you try to disable /MP?

Also, What value do you have in 'maximum number of parallel project builds' ( look at VS Options -> Project and Solutions -> Build and Run ). If it is 8 could you try to set it to 1?

>> This is a statement from your 1st post again:

That wasn't my original post, I was running across the same problem and instead of opening another thread I just tagged along.

>> Could you try to disable /MP?

That seems to work for me; but a rebuild now takes 1h 23 min (in VS 2010 with /MP it was something like 10-15 mins, never actually measured it). That's a workaround only for when I don't change any header files...

Maximum Number of parallel project builds is indeed set to 8. I didn't test setting it to 1 since the first workaround already worked.

Is there anything else I can do/check to help fix this bug? 

>> This is a statement from your 1st post again:

That wasn't my original post, I was running across the same problem and instead of opening another thread I just tagged along.

>> Could you try to disable /MP?

That seems to work for me; but a rebuild now takes 1h 23 min (in VS 2010 with /MP it was something like 10-15 mins, never actually measured it). That's a workaround only for when I don't change any header files...

Maximum Number of parallel project builds is indeed set to 8. I didn't test setting it to 1 since the first workaround already worked.

Is there anything else I can do/check to help fix this bug? 

Hi,

>>...Is there anything else I can do/check to help fix this bug?

I would check:

- Precompile Header settings for all cpp files
- A complete re-build followed by one modification in some source file and compilation with VS setting 'maximum number of parallel project builds' set to 1
- If there are any Machine Generated files by MIDL compiler

MIDL stands for Microsoft Interface Definition Language

I will check your test project 'testforintel-1-with-pch.zip' again.

One more thing...

Could you specify what edition(s) ( Professional, Standard or Express, etc ) of Visual Studio(s) you're using?

>>...That's a workaround only for when I don't change any header files...

Could you try to move all #include directives to a main precompile header file from cpp files? Based on a test case posted some time ago a pch.h file should look like:

[ PCH.H ]

// My PCH

#include "Class01.h"
#include "Class02.h"
...
#include "Class24.h"
#include "Class25.h"

Note: Don't forget to comment or delete all these #include directives in cpp files.

I am using VS 2012 Professional Edition with Update 1, not using the CTP from Novermber 2012. 

The Precompiled Header for .cpp files looks the same in all files I checked; I am not aware of a way to easily check *all* of them.

I don't know what that MIDL-compiler is, so I assume I am not using it.

I switched /MP back on, did a full rebuild, set max number of parallel project builds to 1, changed 1 file and hit "Build": it started recompiling tons of files again, using all 8 processors.

My project consists of a few hundred .cpp-files, no way I can change all of their #include directives.

Small update: After much Internet-research I found one possible culprit could be non-existant headers being referenced in the project. Indeed I had a few of those, once I deleted them there is no more rebuild if I have done no changes and try to run the project. But if I change 1 file it still rebuilds tons of files.

I tried to make sense out of the icl.write.1.tlog; As far as I can tell, each of the files that is unnecssarily being rebuilt is in this file with a "^" in front of the corresponding .obj-file. Also, none of the files without that "°" are being rebuilt. I have no idea what that "^" is supposed to mean or why it would show up on some files and not on others; maybe it can give you some hint as to what the underlying problem really is.

We have fixed the rebuild-issue related to /MP, it should be in the next update (update2).

But about your finding on the none-used header files:

>> Small update: After much Internet-research I found one possible culprit could be non-existant headers being referenced in the project.
>> Indeed I had a few of those, once I deleted them there is no more rebuild if I have done no changes and try to run the project. But if I change 1 file it still rebuilds tons of files.

could you paste some code snippets? which .cpp files contain such header? is it the file that used to generate the pre-compiled header? wouldn't it cause "... file could not be found" compiler-error? 
This would be another different issue.

thanks,
Jennifer

>>...could you paste some code snippets? which .cpp files contain such header?

There is clearly some confusion here. Any chance to post a screenshot?

I understood that Dix is talking about references to some header files in the VS project, not in some cpp files.

>> We have fixed the rebuild-issue related to /MP, it should be in the next update (update2).

That's good to hear! I could ask when that will be available, but the answer will be a variation of the well-known "we can't comment on release dates of future products" :-)

About the header files: Sergey got it right; over the years some files (cpp and header files) got deleted; the cpp files have to be deleted from the project also, else the compiler will complain; but header files dont get compiled per se. And since they don't get included anymore compilation runs normally. Obviously there is something still checking for them, but that doesn't necessarily have to be the Intel Compiler, it is probably MSBuild'd fault; from what I read on the internet that specific error also occures without ICC.

>>...Obviously there is something still checking for them, but that doesn't necessarily have to be the Intel Compiler, it is probably
>>MSBuild'd fault; from what I read on the internet that specific error also occures without ICC.

Thank you for these details. Please wait for a new update and it would be nice if you follow up with a confirmation that the problem is fixed.

Sorry for reiteration... I would also check how Maximum concurrent C++ compilations option ( introduced with VS 2008, VS 2010, etc ) affects the build process. Please take a look at:

Visual Studio -> Tools -> Options -> Project and Settings -> VC++ Project Settings

Just set Maximum concurrent C++ compilations to 1.

Setting the project back to /MP  = YES and setting Maximum concurrent C++ Compilations to 1: Works as it should, no unnecessary recompiles.

>>Setting the project back to /MP = YES and setting Maximum concurrent C++ Compilations to 1: Works as it should,
>>no unnecessary recompiles.

Thanks for the update.

This is a follow up...

I've completed additional investigation and I don't think that your test project with pch is organized properly. Even if you've confirmed that there are no re-compiles please take a look at projects I will attach soon. Projects are based on your ClassXX files and a new structure replicates what you've created. Take a look at how I've set settings for all source cpp files and used ( included ) Stdafx.h header file.

Compilation outputs for Microsoft and Intel C++ compilers with Visual Studio 2005 Professional Edition
will be posted.

Please use these outputs as references after you upgrade the projects to a newer version of Visual Studio.

Here are compilation outputs for Microsoft C++ compiler ( 7 in total / Visual Studio 2005 Professional Edition ):

[ Test 0 - Clean All ]

------ Clean started: Project: ConTestApp, Configuration: Debug Win32 ------
Deleting intermediate files and output files for project 'ConTestApp', configuration 'Debug|Win32'.

[ Test 1 - Complete Re-Build ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Stdafx.cpp
Compiling...
Class20.cpp
Class01.cpp
Class02.cpp
Class03.cpp
Class04.cpp
Class05.cpp
Class06.cpp
Class07.cpp
Class08.cpp
Class09.cpp
Class10.cpp
Class11.cpp
Class12.cpp
Class13.cpp
Class14.cpp
Class15.cpp
Class16.cpp
Class17.cpp
Class18.cpp
Class19.cpp
Generating Code...
Compiling...
ConTestApp.cpp
Compiling manifest to resources...
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 2 - Build - Class10.h modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Class10.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 3 - Build - Class10.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Class10.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 4 - Build - Stdafx.h modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Stdafx.cpp
Compiling...
Class20.cpp
Class01.cpp
Class02.cpp
Class03.cpp
Class04.cpp
Class05.cpp
Class06.cpp
Class07.cpp
Class08.cpp
Class09.cpp
Class10.cpp
Class11.cpp
Class12.cpp
Class13.cpp
Class14.cpp
Class15.cpp
Class16.cpp
Class17.cpp
Class18.cpp
Class19.cpp
Generating Code...
Compiling...
ConTestApp.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 5 - Build - Stdafx.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Stdafx.cpp
Compiling...
Skipping... (no relevant changes detected)
Class20.cpp
Class01.cpp
Class02.cpp
Class03.cpp
Class04.cpp
Class05.cpp
Class06.cpp
Class07.cpp
Class08.cpp
Class09.cpp
Class10.cpp
Class11.cpp
Class12.cpp
Class13.cpp
Class14.cpp
Class15.cpp
Class16.cpp
Class17.cpp
Class18.cpp
Class19.cpp
Compiling...
Skipping... (no relevant changes detected)
ConTestApp.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 6 - Build - ConTestApp.h modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Stdafx.cpp
Compiling...
Class20.cpp
Class01.cpp
Class02.cpp
Class03.cpp
Class04.cpp
Class05.cpp
Class06.cpp
Class07.cpp
Class08.cpp
Class09.cpp
Class10.cpp
Class11.cpp
Class12.cpp
Class13.cpp
Class14.cpp
Class15.cpp
Class16.cpp
Class17.cpp
Class18.cpp
Class19.cpp
Generating Code...
Compiling...
ConTestApp.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

[ Test 7 - Build - ConTestApp.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling...
Stdafx.cpp
Compiling...
Skipping... (no relevant changes detected)
Class20.cpp
Class01.cpp
Class02.cpp
Class03.cpp
Class04.cpp
Class05.cpp
Class06.cpp
Class07.cpp
Class08.cpp
Class09.cpp
Class10.cpp
Class11.cpp
Class12.cpp
Class13.cpp
Class14.cpp
Class15.cpp
Class16.cpp
Class17.cpp
Class18.cpp
Class19.cpp
Compiling...
ConTestApp.cpp
Linking...
Embedding manifest...
ConTestApp - 0 error(s), 0 warning(s)

Here are compilation outputs for Intel C++ compiler ( 7 in total / Visual Studio 2005 Professional Edition ):

[ Test 0 - Clean All ]

------ Clean started: Project: ConTestApp, Configuration: Debug Win32 ------
Deleting intermediate files and output files for project 'ConTestApp', configuration 'Debug|Win32'.

[ Test 1 - Complete Re-Build ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Stdafx.cpp
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
ConTestApp.cpp
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Class20.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class19.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class18.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class17.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class16.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class15.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class14.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class13.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class12.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class11.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class10.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class09.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class08.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class07.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class06.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class05.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class04.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class03.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class02.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class01.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Compiling manifest to resources... (Microsoft VC++ Environment)
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
xilink: executing 'link'
ConTestApp - 0 error(s), 0 warning(s), 20 remark(s)

[ Test 2 - Build - Class10.h modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Class10.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
ConTestApp - 0 error(s), 0 warning(s), 1 remark(s)

[ Test 3 - Build - Class10.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Class10.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
ConTestApp - 0 error(s), 0 warning(s), 1 remark(s)

[ Test 4 - Build - Stdafx.h modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Class20.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class19.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class18.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class17.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class16.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class15.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class14.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class13.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class12.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class11.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class10.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class09.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class08.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class07.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class06.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class05.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class04.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class03.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class02.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class01.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
ConTestApp - 0 error(s), 0 warning(s), 20 remark(s)

[ Test 5 - Build - Stdafx.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Stdafx.cpp
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
ConTestApp.cpp
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
Class20.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class19.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class18.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class17.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class16.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class15.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class14.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class13.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class12.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class11.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class10.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class09.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class08.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class07.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class06.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class05.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class04.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class03.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class02.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Class01.cpp
Warning #673: the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
ConTestApp - 0 error(s), 0 warning(s), 20 remark(s)

[ Test 6 - Build - ConTestApp.h modified ]

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

[ Test 7 - Build - ConTestApp.cpp modified ]

------ Build started: Project: ConTestApp, Configuration: Debug Win32 ------
Compiling with Intel(R) C++ Compiler XE 12.1.3.300 [IA-32]... (Intel C++ Environment)
ConTestApp.cpp
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
ConTestApp - 0 error(s), 0 warning(s), 0 remark(s)

Try to print compilation outputs for Microsoft and Intel C++ compilers and compare.

Note 1: Atached zip file has two Visual Studio 2005 projects.

Note 2: I do not know why the warning #673:
...
...the initial sequence of preprocessing directives is not compatible with those of precompiled header file "Debug\ConTestApp.pchi"
...
is displayed after the project was converted for use with Intel C++ compiler.

Allegati: 

AllegatoDimensione
Download contestapp.zip22.94 KB

I have the same issue. I have tried all updates of C++ compiler in 2013, from 2 to 5.

Compiler rebuilds everything even if there are no changes in the project whatsoever. Multi-processor compilation /MP doesn't work at all - compiler always works in one thread no matter what Maximum concurrent C++ compilations is set to.

MSVC 2010 has no problems with the same project. I see that this problem was detected in 2012 and no solution is available still?

Now my projects compiles 7-10 minutes, productivity is zero, very disappointed.

Is there any way to return money back I paid for the compiler?

Multiprecision Computing Toolbox for MATLAB

Could you create a small reproducer? Thanks in advance.

A fix has been implemented in the 14.0 and 15.0 from a different test case. Please try the latest 14.0 or 15.0 update with your application. Let us know if it is still an issue.

Thanks, Jennifer

Lascia un commento

Eseguire l'accesso per aggiungere un commento. Non siete membri? Iscriviti oggi