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 :This issue has been fixed in the latest 11.1 update and newer compiler versions.

[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.]



For more complete information about compiler optimizations, see our Optimization Notice.