Intel Software Network articles feed http://software.intel.com/en-us/articles/intel-c-compiler-for-windows-kb/software-defects/ en-us Warning #677: memory usage conflict with precompiled header file seen on Windows* XP and Linux*
Reference Number : DPD200136749


Version : 10.1, 11.0, 11.1


Product : Intel® C++ Compilers Professional Edition for Windows* and Linux*.  Intel ® Parallel Composer.


Operating System : Windows* versions prior to Windows Vista* or equivalent, Linux*


Problem Description : When using precompiled headers, you may see the diagnostic:

Warning #677: memory usage conflict with precompiled header file

This means that there was an internal problem with the precompiled header processing in the compiler and precompiled headers will not be used for the file in question which may cause an increase in build times.


Resolution Status : We are investigating this issue.  Please contact us via the User Forum or Intel® Premier Support if you are experiencing this issue.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/warning-677-memory-usage-conflict-with-precompiled-header-file-seen-on-windows-xp-and-linux Thu, 22 Oct 2009 15:35:39 -0700 http://software.intel.com/en-us/articles/warning-677-memory-usage-conflict-with-precompiled-header-file-seen-on-windows-xp-and-linux#comments http://software.intel.com/en-us/articles/warning-677-memory-usage-conflict-with-precompiled-header-file-seen-on-windows-xp-and-linux Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Thread affinity compiler switches have no effect
Reference Number : DPD200119846


Version : 
Intel® C++ Compiler for Linux*and Windows*, 11.1 initial releases and update 1
Intel® Fortran Compiler for Linux*and Windows*, 11.1 initial releases and update 1


Operating System : Microsoft Windows XP*, Microsoft Windows Vista*, Microsoft Windows Server 2003*; Red Hat Enterprise Linux* 3, 4, 5, SUSE LINUX Enterprise Server* 9, 10, 11, other supported Linux distributions (see Release Notes)


Problem Description :  Thread affinity compiler switches /Qpar-affinity (Windows*) or -par-affinity (Linux*) are used to specify compiled-in thread affinity of the executable.  However, when the executable is run, no effect is observed.  In other words, the default runtime thread affinity is used, or if KMP_AFFINITY has been set, the runtime thread affinity matches its setting (the switches are supposed to take precedence).


Resolution Status : The issue has been resolved in the 11.1 update 2 release.  The compiler builds are:
Linux* C++: l_cproc_p_11.1.056
Linux* Fortran: l_cprof_p_11.1.056
Windows* C++: w_cproc_p_11.1.046
Windows* Fortran: w_cprof_p_11.1.046



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/thread-affinity-compiler-switches-have-no-effect Thu, 24 Sep 2009 10:39:53 -0700 http://software.intel.com/en-us/articles/thread-affinity-compiler-switches-have-no-effect#comments http://software.intel.com/en-us/articles/thread-affinity-compiler-switches-have-no-effect Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Unresolved External Symbol Error at Link Phase when Enabled "/Qlong_double"
Reference Number : DPD200084693


Version : 11.1.038


Operating System : Windows


Problem Description : 

Following case will get unresolved external symbol error at linking stage if use c++ stream to pass numerical variables with option /Qlong_double specified.

Case: test006.cpp
#include <stdio.h>
#include <iostream>
using namespace std;
int main()
{
            int x=0;          //line 6
            cout << x;      //line 7
}


Command:

icl /Od /Ob1 /Qlong_double /MDd test006.cpp 


Fail Output:

 -out:test006.exe
test006.obj
test006.obj : error LNK2001: unresolved external symbol "protected: virtual class std::ostreambuf_iterator<char,struct std::char_traits<char> > __thiscall std::num_put<char,class std::ostreambuf_iterator<char,struct std::char_traits<char> > >::do_put(class std::ostreambuf_iterator<char,struct std::char_traits<char> >,class std::ios_base &,char,UNKNOWN)const " (?do_put@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@MBE?AV?$ostreambuf_iterator@DU?$char_traits@D@std@@@2@V32@AAVios_base@2@D_T@Z)
test006.exe : fatal error LNK1120: 1 unresolved externals

 

While if changing line 6 & 7 to following,  the test will link fine: 

char x='0';          //line 6
cout << x;          //line 7


Currently only using the option combination like "/Ob{1|2} /Qlong_double /MD[d]" and the use of C++ stream to pass numerical variable will trigger this link failure.  


Resolution Status : 
This is a regression from C++ Compiler 11.0 regarding a new feature on 11.1:
"The post-11.0 handling of dllimport and inline, decides not to emit the funciton definition in this case, because it is expected to be supplied from the DLL. You can get the 11.0 and before behavior back by using /mGLOB_cg_lower_dllimport=F."

Other possible work-arounds are:
1. Use /Ob0 while using /Qlong_double.
2. Avoid the use of C++ stream to pass numerical variables. In this case use printf instead.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

]]> http://software.intel.com/en-us/articles/unresolved-external-symbol-error-at-link-phase-when-enabled-qlong_double Wed, 19 Aug 2009 02:19:50 -0700 http://software.intel.com/en-us/articles/unresolved-external-symbol-error-at-link-phase-when-enabled-qlong_double#comments http://software.intel.com/en-us/articles/unresolved-external-symbol-error-at-link-phase-when-enabled-qlong_double Intel® Compilers Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Stack Frame Run-time Check incompatible with Microsoft* Visual C++ x64
Reference Number : DPD200084262


Version : 11.1.038 for Windows running on Intel(R) 64


Operating System : Windows x64 edition


Problem Description : 
The following program will get stack frame Run-Time Check(RTC) failure due to incompatible RTC stack frame check between Intel C++ Compiler for Windows and Microsoft* Visual C++ 2005 or 2008 for x64 run time library.

--- Program ---
void sub();

int main(int argc, char* argv[])
{
  sub();
  return 0;
}

void sub()
{
  int i;
  __declspec(align(64)) float aiueo[256];

  for (i=0;i<256;i++)
    aiueo[i] = 0;

  return;
}

--- RTC error message ---

Run-Time Check Failure #2 - Stack around the variable 'result.38007' was corrupted.

--- problem definition ---

If array "aiueo" is defined as align(32), align(64) or above, this failure will expose. If array "aiueo" is defined as align(8), align(16), this failure will be avoided.

This is a stack frame Run-Time Check(RTC: /RTCs) incompatible issue between Intel C++ Compiler for Windows and Microsoft Visual C++ Compiler for x64 platform run time library. The program binary is actually gengerated correctly.

Resolution Status : 

This has been fixed in the 11.1.046 C++ Compiler for Windows.

 

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/stack-frame-run-time-check-incompatible-with-microsoft-visual-c Sun, 02 Aug 2009 20:03:08 -0700 http://software.intel.com/en-us/articles/stack-frame-run-time-check-incompatible-with-microsoft-visual-c#comments http://software.intel.com/en-us/articles/stack-frame-run-time-check-incompatible-with-microsoft-visual-c Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base How to create a preprocessed file (.i file) Usually when there's a compiler bug, we will need a testcase. Otherwise we won't be able to find the problem and verify the fix.

Because we won't be able to have the same environment as yours, we will need either a testcase or a preprocessed file (.i file).

Sometimes a small testcase may not always duplicate the problem. And also you may not have the time to create a testcase. So a preprocessed file would work in such case.


Note about a proprocessed file (.i file): it contains all the source code in original .cpp/.c as well as all the needed header files. The compiler (icl or cl) generates the code based on the compile options and include files. So the .i file generated by icl.exe is most likely different than the one generated by cl.exe.

To create a preprocessed file (.i file), just add "-EP -P" to the compile option, and recompile the original .cpp file.  You can also generate a .i file directly from the "Prepocessor" property in Visual Studio*:

  • Right click the file name, and click properties
  • Click Preprocessor\Generate Preprocessed File\Without Line Numbers (/EP /P)

if you recompile from a command window, the .i file will be created under the current directory.

if you recompile from within the Visual Studio* IDE, the .i file will be created under the directory where the original source file is located.

]]> http://software.intel.com/en-us/articles/how-to-create-a-preprocessed-file-i-file Thu, 23 Jul 2009 09:29:11 -0700 http://software.intel.com/en-us/articles/how-to-create-a-preprocessed-file-i-file#comments http://software.intel.com/en-us/articles/how-to-create-a-preprocessed-file-i-file Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base compiler internal error 0_1279
Reference Number : DPD200008448, DPD200137998


Version : All the 10.x, 11.x compilers and the older versions.


Operating System : Linux, Windows


Problem Description : 
    Test case 1: test.c
             int round(float in);
             int foo(float in)
             {
                  int res=round(in);
                  if(res !=0) res = 1;
                   return res;
              }

        Test case 2: test.c
              float memcpy(char*, char*, int);
              float res;
              void foo(char* in, char* out)
              {
                   res = memcpy(in, out, 100);
              }
     Test case 3: test.c
             double pow();
             void bar(double);
             void foo()
             {
                  int a=0;
                  int b[1]={255};
                  bar(pow(b[a],2));
             }
     compile the test case: icl test.c -c
The compiler will report the internal error 0_0, or the internal error 0_1279, or the internal error 0_1208 etc in difference cases.
This is the problem in all the cases where the compiler recognize something (defined by user differently than in compiler intrinsics table) being an intrinsic call and expand this call inline.
Resolution Status : 
1. Change the function name to your own name different to the compiler intrinsic function. For example, change 'round' in case 1 to 'myround', change 'memcpy' in case 2 to 'mymemcpy', change 'pow' in case 3 to 'mypow'.
2. Include the compiler head files to use the intrinsic functions provided by compiler instead of to define your own. Be carefull to the compiler warnings for incompatible declarations during compilation stage.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/compiler-internal-error-0_1279 Mon, 20 Jul 2009 19:50:24 -0700 http://software.intel.com/en-us/articles/compiler-internal-error-0_1279#comments http://software.intel.com/en-us/articles/compiler-internal-error-0_1279 Intel® Parallel Composer Intel® Compilers Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Internal Compiler Error
Problem Description

A compilation fails with a message similar to one of the following:

example.c(22): internal error:

Please visit 'http://www.intel.com/software/products/support' for assistance.

[ Aborting due to internal error. ]

compilation aborted for example.c (code 1)

 

or

catastrophic error: **Internal compiler error: internal abort**

Please report this error along with the circumstances in which it occurred in a Software Problem Report.

Note: File and line given may not be explicit cause of this error.

compilation aborted for example.f90 (code 3)

 

Explanation

This message usually indicates a compiler defect.

Please report the problem to Intel through the Intel® Software Network Forums or Intel® Premier Support (support license and registration required). You will need to supply a test case along with a list of the compile options used and the exact compiler version that shows the problem. If you are not using a current compiler version, try the most recent version available to you as the error may have already been corrected.

Please note that this message is generic in nature and does not have a single cause nor solution. Providing a test case that reproduces the error is the only way to get a precise analysis of the problem.

In some, but not all, cases, you can work around the error by reducing the optimization level. You may find it helpful to try compiling with fewer switches to see if you can find one that, when removed, eliminates the error. It is also helpful to remove or comment out portions of the source file to see if you can isolate the line or lines that trigger the problem. The smaller the test case, the easier it will be for Intel to resolve the problem.

 

 

 

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

 

]]> http://software.intel.com/en-us/articles/internal-compiler-error Thu, 02 Jul 2009 10:24:50 -0700 http://software.intel.com/en-us/articles/internal-compiler-error#comments http://software.intel.com/en-us/articles/internal-compiler-error Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Unable to set compiler option /Qfp-speculation from IDE
Reference Number : 
U66541 / DPD200137349

Version : 
Intel C++ compiler 11.1.035


Operating System : 
Windows


Problem Description :

When I change the project property in VS2003 to set the /Qfp-speculation to safe, the result in command line is not "/Qfp-speculation:safe", it is appearing as "/Qfp-speculationsafe" and we get error during compilation.

Resolution Status :


One needs to provide an argument to compiler /Qfp-speculation. The valid arguments are fast, safe, strict and off. The compiler option /Qfp-speculation from IDE is not being set properly. You may set this option from command line property page as work around.

We have tried /Qfp-speculation:safe in VS2008 from command line and there is no issue.




[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/unable-to-set-compiler-option-qfp-speculation-from-ide Thu, 02 Jul 2009 10:13:29 -0700 http://software.intel.com/en-us/articles/unable-to-set-compiler-option-qfp-speculation-from-ide#comments http://software.intel.com/en-us/articles/unable-to-set-compiler-option-qfp-speculation-from-ide Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Access violation error when registering a DLL using regsrv32 or loading a DLL using LoadLibrary()
Reference Number : DPD200050564


Version : 10.1, 11.0


Operating System : Windows


Problem Description :

You may get an access violation error when using regsvr32 to register a DLL or using LoadLibrary() function to load a DLL if both of the following conditions apply:
  1. The DLL contains calls to Intel(R) IPP functions and IPP functions use Intel OpenMP library for threading; or the DLL uses the Intel OpenMP library directly.
  2. The DLL is built with Intel(R) C++ Compiler version 10.1 with package ID w_cc_p_10.1.029 or version 11.0 with package ID w_cproc_p_11.0.066, or earlier.

Resolution Status :
This issue has been resolved in the Intel(R) C++ Compilers version 10.1 with package ID w_cc_p_10.1.030 and version 11.0 with package ID w_cproc_p_11.0.072 or higher.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/regsrv32-fails-when-registering-a-dll-built-with-icl Fri, 24 Apr 2009 11:53:04 -0700 http://software.intel.com/en-us/articles/regsrv32-fails-when-registering-a-dll-built-with-icl#comments http://software.intel.com/en-us/articles/regsrv32-fails-when-registering-a-dll-built-with-icl Intel® C++ Compiler for Windows* Knowledge Base Project properties changed when configuring to use Intel C++ Compiler
Reference Number : DPD200036725, DPD200037715


Version : 10.x


Operating System : Windows*


Problem Description : 
When switching to use the Intel C++ Compiler, some project properties got changed.

This is because in the 10.x version the IDE integration maintains all the project properties in the .icproj file. So there're times that a sync operation between .icproj and .vcproj is needed.

Resolution Status : 
This is fixed in 11.0 version of the Intel C++ Compiler for Windows.

In the 11.0 the IDE integration only saves the Intel C++ Compiler specific properties in the .icproj file, all the original Visual C++ project properties are untouched in the .vcproj file.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/project-properties-changed-when-configuring-to-use-intel-c-compiler Tue, 14 Apr 2009 12:58:49 -0700 http://software.intel.com/en-us/articles/project-properties-changed-when-configuring-to-use-intel-c-compiler#comments http://software.intel.com/en-us/articles/project-properties-changed-when-configuring-to-use-intel-c-compiler Intel® C++ Compiler for Windows* Knowledge Base