Intel Software Network articles feed http://software.intel.com/en-us/articles/intel-c-compiler-for-windows-kb/known-issues/ en-us Intel® Professional Edition Compilers 11.1 Fixes List http://software.intel.com/en-us/forums or submit an issue to Intel Premier Support, https://premier.intel.com.  The fixes list for Intel® IPP Library 6.1 can be found here.

Update 3 (Posted October 2009), Package IDs below

l_cproc_p_11.1.059
l_cprof_p_11.1.059
m_cproc_p_11.1.076
m_cprof_p_11.1.076
w_cproc_p_11.1.051
w_cprof_p_11.1.051

DPD200005308 Fortran Access violation with OpenMP and debug option enabled
DPD200012215 C, C++, Fortran documentation about application register access is vague
DPD200021013 C, C++ compiler mistakenly assumes all sources compiled with same set of options
DPD200033150 Fortran Slow compile
DPD200038801 Fortran Incorrect Static Verifier error message 12224
DPD200039280 Fortran Static Verifier produces invalid warning for optional Fortran argument
DPD200048138 Fortran Invalid Debug Information message shown for DLLIMPORTed COMMON variables
DPD200049461 C Bogus error #12048 on safe negative index
DPD200049575 C++ bogus error #12178 on used local const with -diag-enable sv3
DPD200049579 C++ Static Verifier:incorrect error
DPD200082641 Fortran READ statement doesn't return correct completion status
DPD200082921 Fortran Access violation in case the malloc from C code is used to allocate the memory
DPD200083739 C Incorrect variable substitution during optimization cross branches
DPD200085342 C internal error - backend signals on both Linux and Windows version of 11.1
DPD200085556 Fortran iidb uses 100% of CPU while waiting for input
DPD200085613 C icc don't accept --exclude-libs linker flag
DPD200110443 Fortran UNROLL_AND_JAM directive ignored or not working as expected on triple-nested DO-LOOP
DPD200110916 C++ Microsoft and Gnu compatibility on allowing pure virtual specifiers in prototype instantiations
DPD200112090 Fortran Incorrect pointer with OpenMP at -O0
DPD200118525 Fortran Visual Studio Project: Source Code Control glyphs not automatically updated
DPD200119954 Fortran demo default startup project not correct
DPD200121416 C++ Profile Guided Optimization: 12% performance drop
DPD200136609 Fortran Loop distribution caused Incorrect results when using ifort -i8 -r8 -openmp
DPD200136761 C++ Optimizer not disambiguating memory as well, leading to more memory accesses then in 11.0
DPD200136823 C++ #pragma disable does not disable first instance of #pragma outside of code block
DPD200136891 Fortran Problem with using dynamically allocated arrays in OpenMP reduction clause
DPD200136984 Fortran MKL library for wrong calling convention gets linked on command line
DPD200136996 C++ (0): internal error: backend signals
DPD200137044 C++, C Linux: wint_t not defined in stddef.h
DPD200137266 C++ problem with template dependent name processing and default params
DPD200137318 C, C++ /Qprof-psa-* options should be removed from /help
DPD200137464 Fortran Internal compiler error (C0000005)
DPD200137508 Fortran Run-Time Library: error on namelist for internal file write
DPD200137584 Fortran -fpe0 and -fltconsistency interaction
DPD200137763 C, C++ Incorrect error when building with -diag-enable sc-parallel
DPD200137967 Fortran Link error for already defined (duplicate) symbol with type-bound procedures and /Od
DPD200138038 Fortran Incorrect name decoration for EQUIVALENCEd module symbols
DPD200138085 Fortran Procedure pointer component and debug symbols cause internal compiler error or CPU-bound compilation
DPD200138089 Fortran Debugger shows wrong value for component of polymorphic type
DPD200138527 Fortran SEQUENCE type adds padding before UNION
DPD200138674 Fortran Internal Compiler Error when accessing an overloaded interface
DPD200138694 Fortran Internal compiler error involving type bound procedure
DPD200138746 Fortran Nested derived type with POINTER causes internal compiler error in Loop Multiversioning
DPD200138828 C, C++ internal error: 0_1561
DPD200138845 Fortran Compiler hang at exiting from compilation error.
DPD200138870 Fortran Feature Request: -opt-report should report COMMON blocks splitting (which can happen with -ipo)
DPD200138937 Fortran -ftrapuv does not catch divide-by-zero in Where clause with real array size < 8, and incorrect behavior for array size >= 8
DPD200138944 Fortran IMPLICIT NONE gives error for contained procedure argument that is CALLed
DPD200139029 Fortran STOP 0 in Windowing application results in Error 38 to CONOUT$
DPD200139383 C, C++ Regression with libirc_s.a, ld duplicated symbol error
DPD200139390 C internal compiler error on 64-bit code in linux kernel
DPD200139418 C++ error #409: "T2::T2()" provides no initializer for: const member "T2::t1"
DPD200139432 C, C++ "internal error: 0_1149" when using /fp:fast
DPD200139458 C++ ICC can't compile file due to friend class declaration with nontype template argument
DPD200139473 Fortran "/debug:parallel" is not added to the command line for Fortran when /Zi selected
DPD200139530 Fortran Internal Compiler Error when routine called with derived type argument inside ASSOCIATE construct
DPD200139531 Fortran Internal Compiler Error with /Qfp-stack-check on Intel64
DPD200139541 C, C++ assertion failure with overloaded function call and using declaration in dependent name processing
DPD200139555 Fortran IPO link invokes ld twice, the first instance generates "ld: no input files" failure
DPD200139577 C++ backend signals internal compiler error at -O2
DPD200139608 Fortran ENDFILE gives error for stream access file
DPD200139624 C++ (0): internal error: backend signals in termination test in openmp iterator loop
DPD200139640 C++ template argument deduction problem with const template operator
DPD200139696 Fortran Parsing error for variable named PROCEDURE
DPD200139700 Fortran Dummy argument mismatch error for passed procedure with CLASS(*) argument
DPD200139701 Fortran Internal compiler error for pointer assignment to type-bound procedure
DPD200139745 Fortran Internal compiler error for call passing class(*) object and procedure
DPD200139785 Fortran FPP: Comment appearing between fpp directives causes incorrect parsing of #ifdef directive
DPD200139935 C, C++ Internal error: backend signals
DPD200139947 Fortran Internal compiler error: segmentation violation signal raised
DPD200139986 Fortran Internal Compiler Error during High Level Optimization while compiling at O3 but not at O2, regression in 11.1.046
DPD200140001 Fortran VS2008 throws External component has thrown an exception error when creating new Fortran project
DPD200140037 Fortran Seg Fault after Mem-op Detection optimization phase
DPD200140069 Fortran Internal Compiler Error when compiling with 11.1 versions, not with 11.0.074
DPD200140117 Fortran Possible infinite loop or memory leak at compilation time in Loop fusion
DPD200140128 Fortran FPP: Fundamental confusion with fpp and macro expansion leads to #error: '#ifdef' argument starts with wrong symbol.
DPD200140234 Fortran Internal Compiler Error with Mac OS 11.1.067 compile
DPD200140243 Fortran Internal Compiler Error at -O2 or higher on IA-32, no error on Intel 64 but no loop vectorization
DPD200140550 C Internal compiler error in Code Generator

Update 2 revised (Posted October 2009), Package IDs below

w_cproc_p_11.1.048
w_cprof_p_11.1.048

DPD200139120 C, C++, Fortran - The packages were rebuilt to correct an issue where the compiler would not run on certain Windows 7* and Windows Server 2008* systems. Correctness of the generated code is not an issue.


Update 2 (Posted September 2009), Package IDs below

l_cproc_p_11.1.056
l_cprof_p_11.1.056
m_cproc_p_11.1.067
m_cprof_p_11.1.067
w_cproc_p_11.1.046
w_cprof_p_11.1.046

DPD200003663 C, C++ Access mechanism inconsistency for #pragma section()/__declspec(allocate()) problems.
DPD200007737 Fortran HLO causes incorrect results only with Intel® Core™ Duo processor and 32 bit version of compiler
DPD200017249 C Linux* kernel: Feature Request: support __builtin_trap intrinsic
DPD200022129 C O2 problem
DPD200022902 C, C++, Fortran wrong compiler annotation with -prof_use
DPD200032138 C, C++ Regression in 10.0 auto-parallelizer
DPD200041387 C++ Performance regression with 11.0 Beta compiler at -O3 -ipo PGO.
DPD200042107 C, C++ compile time 100x Microsoft Visual C++ 7.0 - long optimization time
DPD200045100 C IDB fails to load executable - libthread_db.so.1 undefined symbol ps_lgetfpregs
DPD200048386 Fortran Procedure pointers are not distinct from integers in TKR signature resolution
DPD200048780 Fortran Incorrect address handed to C-Fortran interoperable function
DPD200048863 Fortran ifort 11.0 BIND(C,name="") produces object files with empty symbol names
DPD200049434 C++ Bogus warning #12174 on a function declared noreturn
DPD200050515 C++ Compiler Intrinsic missing from header file and documentation
DPD200050739 C, C++ symbol info reload performance unacceptable for large applications
DPD200051151 Fortran, C++, C FLEXlm server fails to start on Windows* Server 2008 x64
DPD200083317 Fortran Array constructor [,,] is not thread safe
DPD200083894 Fortran Custom build step feature doesn't work in case there are specific symbols in the pathname
DPD200084262 C stack run time check reports failure for alignment greater than 64
DPD200111195 Fortran RANDOM_NUMBER is not threadsafe
DPD200111308 C++ Cannot specify sets of OS procs with {} in proclist with KMP_AFFINITY=explicit
DPD200111309 C, C++, Fortran Need consistent correspondence between OMP hread ids and global thread ids in non-nested code
DPD200111314 C, C++, Fortran Error initializing foreign thread's OMP affinity mask
DPD200112213 Fortran OpenMP causes seg fault with contains subroutine
DPD200117988 Fortran 11.1 beta get segmentation fault
DPD200118875 Fortran ifort 11.0 benchmark fails to validate on IA-64
DPD200119435 C Need PIC version of libimf.a
DPD200120466 C Unix (gcc feature not in icc): missing many chk __builtin___ rouitines
DPD200120952 C++ OpenMP task crashes with new class statement in Debug mode
DPD200121133 C Resulting generated code gets different results with -O2 and -O3
DPD200121218 C, C++, Fortran linking -lm before objects calling math functions results in GNU libm math functions being used instead of Intel libimf functions
DPD200121498 Fortran Local array with allocatable components not deallocated on routine exit
DPD200135534 Fortran ifort mainline lost optimization of product reduction
DPD200135655 C++ Compiler packaging error when installed by non-root user
DPD200135696 C unresolved symbol with /Qipo in 11.x only - 10.x works
DPD200135929 C++ Software Pipelining causes runtime segmenation fault.
DPD200135962 Fortran Correct test with allocatable character array produces SegV.
DPD200135966 C++ icc warning level is incompatible with vc warning level
DPD200135967 C++ Code Generator SCH Postpass cause memory ambiguation.
DPD200136024 C++ runtime segmentation fault in PGO + IPO build.
DPD200136315 C++ Slow compile time - icc 11.1 average 2.7x slower than gcc3.4
DPD200136339 C icc takes too long to compile a .c file
DPD200136540 C runtime crash when /Qnum-opt 25
DPD200136675 C icc 11.1 generates code that has a reference to __moddi3
DPD200136711 C++ gcc compatibility - diff in priority of -I and -isystem
DPD200136754 C, C++ icc unable to find framework include when isysroot is set
DPD200136776 C++, C "(0): internal error: 0_0" with multi-source compilation
DPD200136806 Fortran Can't set large values for REAL*8 in tooltips
DPD200136846 C++ icpc fails to compile the test case with --permissive
DPD200136852 C++ icpc, g++ 4.3.0 and __builtin_isfinite
DPD200136877 Fortran Error for pointer assignment of ASSOCIATE name for dummy argument of PURE subroutine
DPD200136885 Fortran Implicit typing happens in the wrong scope
DPD200136909 C++ Optimization generates incorrect code
DPD200136951 C++ 0x5C Japanese Character Issue
DPD200136972 Fortran Error with ALARM-Portability Function.
DPD200137145 Fortran Deferred-length character should not require /assume:realloc_lhs
DPD200137215 Fortran Variable name CLASS confuses parser
DPD200137216 Fortran Regression - typing floating point expression into debugger Watch window crashes Microsoft Visual Studio*
DPD200137220 Fortran Customers report .F and .FOR files appear as free-form source in Visual Studio text editor as of 11.1
DPD200137276 C++ Code generation problem
DPD200137279 Fortran Internal Compiler Error with /gen-interfaces
DPD200137347 Fortran IFORT does not accept derived type name starting with "is"
DPD200137404 C, C++, Fortran Installation stalls at license agreement on MAC 11.1
DPD200137410 Fortran /fpscomp:filesfromcmd does not work if null argument provided.
DPD200137424 Fortran No code generated for call to elemental type-bound procedure with no arguments
DPD200137428 Fortran Internal Compiler Error with 11.1.038
DPD200137453 Fortran File ACTION='READWRITE' does not allow second process to open file for writes
DPD200137485 Fortran Error: for_array_copy_in/for_array_copy_out again
DPD200137518 Fortran Conflicting attributes error for protected allocatable character
DPD200137527 C, C++ icc does not accept -Wstrict-aliasing=2
DPD200137545 C, C++ Linux kernel: icc emits undefined symbol, while gcc doesn't
DPD200137552 Fortran internal compiler error (C0000005)
DPD200137598 Fortran Incorrect results at -O3 with specific optimization
DPD200137625 Fortran Assignment of array constructor to allocatable array component does not reallocate left side
DPD200137666 C Regression test suite fails with icc 11.0, 11.1 but is fine with 10.1 and earlier versions
DPD200137681 Fortran Problem with 2-byte characters in NAMELIST input data when using static debug libraries
DPD200137687 Fortran Error #10106 for valid code
DPD200137715 Fortran Concatenation of deferred-length character component of derived type gives garbage result
DPD200137735 C++, C String layout on Mac OS X* Leopard/Snow Leopard for 64-bit
DPD200137781 C++ Need scalar var privatization support for std::complex data type with func call
DPD200137862 Fortran Format compiles incorrectly
DPD200137880 C++, C driver link in libirc.a twice resulting in duplicated symbols at link time
DPD200138020 Fortran Wrong executing results after compiling
DPD200138029 Fortran ifort linux Intel 64 11.1.046 Internal Compiler Error
DPD200138035 C++ icc produces bad x86_64 Mach-O relocation entries
DPD200138042 Fortran write routine is consuming all of memory and crashing the system
DPD200138087 Fortran Assignment of derived type with allocatable scalar and type-bound procedure causes access violation
DPD200138144 C, C++ ipo build reports unresolved ___builtin_object_size symbol
DPD200138343 C, C++ "(0) internal error: backend signals" with openmp on "while"
DPD200138406 C, C++, Fortran Shared libraries flagged as needing executable stacks prevents being loaded when SELinux enabled
DPD200138415 Fortran Bad debug information for Fortran array variable
DPD200138447 C Executing wrong code path at O2
DPD200138449 Fortran ifort 11.1 internal compiler error on module with recursive subroutine containing CLASS pointer
DPD200138493 OSR: illigal SIGN extend removal around UNSIGNED value in strength reduction
DPD200138568 Fortran vec-report3 or 4 or 5 on 11.1 Mac OS X* Compiler Pro causes bogus DWARF error
DPD200138583 C internal compiler error: Creating constant of incorrect size
DPD200138584 C assertion in compiler
DPD200138607 Fortran Internal compiler error during compile of large source file under 11.1 compilers
DPD200138609 C++ Compiler fails to select correct template function
DPD200138632 Code coverage with unwind handler
DPD200138634 Fortran OpenMP directive causes internal compiler error with ifort 11.1.046
DPD200138649 Fortran incorrect debug info for subroutine array parameter
DPD200138652 Fortran Internal compiler error related to multifaceted derived type structures
DPD200138663 C++ Compiler Error: Gnu-style asm must use __asm__ keyword when -use_msasm is specified
DPD200138665 Fortran internal read not working with 11.1
DPD200138738 C, C++ ICC not differentiating between USER_HEADER_SEARCH & HEADER_SEARCH paths
DPD200138791 Fortran Inlining a subroutine containing an OpenMP parallel region destroys associated status of pointer argument
DPD200138893 Fortran Memory leak on assignment of derived types with allocatable components
DPD200138899 Fortran MAXLOC intrinsic bug on IA-64 processor
DPD200138901 Fortran Internal compiler error at -O3 but not -O2 for 11.1.046
DPD200138938 Fortran ifort 11.1 -debug internal compiler error on module with procedures bound by name
DPD200139006 C++ Error during project conversion
DPD200139120 C, C++ the application hang due to xgetbv in __intel_cpu_indicator_init()

* Other names and brands may be claimed as the property of others.
]]> http://software.intel.com/en-us/articles/intel-professional-edition-compilers-111-fixes-list Thu, 05 Nov 2009 13:37:23 -0800 http://software.intel.com/en-us/articles/intel-professional-edition-compilers-111-fixes-list#comments http://software.intel.com/en-us/articles/intel-professional-edition-compilers-111-fixes-list ISN General 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® Visual Fortran Compiler for Windows* Knowledge Base Compiler issues the message &#34;Catastrophic error: unable to obtain mapped memory (see pch_diag.txt) &#34;
Reference Number : DPD200141164


Version : 11.1


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


Operating System : All x64 versions of Windows*


Problem Description : When building a Visual Studio 2005 or 2008* generated MFC Application or a MFC ActiveX Control, the compiler reports the following message:

Catastrophic error: unable to obtain mapped memory (see pch_diag.txt)

This means that there was an internal problem with the precompiled header processing in the compiler.  This problem has been seen only in the 64-bit versions of Windows* and only with the x64 project configurations.


Resolution Status : This issue has been resolved and the solution will be provided in a future compiler update.  As a temporary workaround please use the compiler option "/Q_multisrc-" .  The "/Q_multisrc-" option may add to the overall compilation time.



[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-issues-the-message-catastrophic-error-unable-to-obtain-mapped-memory-see-pch_diagtxt Thu, 22 Oct 2009 17:00:28 -0700 http://software.intel.com/en-us/articles/compiler-issues-the-message-catastrophic-error-unable-to-obtain-mapped-memory-see-pch_diagtxt#comments http://software.intel.com/en-us/articles/compiler-issues-the-message-catastrophic-error-unable-to-obtain-mapped-memory-see-pch_diagtxt Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base 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 Catastrophic error: could not open source file &#34;gmmintrin.h&#34;

Reference Number :  DPD200140118

Version : 11.1

  •  
    • Intel C++ and Fortran Compiler for Linux* 11.1
    • Intel C++ and Fortran Compiler for Mac OS* X 11.1
    • Intel C++ and Visual Fortran Compiler for Windows* 11.1

Operating System : 

Linux*, Mac OS* X, Windows*

Problem Description : 
The documentation in the 11.1 update2 compiler says the header file for Intel® AVX intrinsics is "gmmintrin.h". It is wrong.

If you use it, you will get following compile error:

>>icl /c /Od /EHsc t.cpp
Intel(R) C++ Compiler Professional for applications running on IA-32, Version 11.1    Build 20090903 Package ID: w_cpro
_p_11.1.046
Copyright (C) 1985-2009 Intel Corporation.  All rights reserved.

t.cpp
t.cpp(3): catastrophic error: could not open source file "gmmintrin.h"
  #include <gmmintrin.h>
                        ^

compilation aborted for t.cpp (code 4)



Resolution Status : 

This is a known bug. It will be fixed in the future compiler update.

Please use the correct header file "immintrin.h".

[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/catastrophic-error-could-not-open-source-file-gmmintrinh Fri, 25 Sep 2009 09:13:49 -0700 http://software.intel.com/en-us/articles/catastrophic-error-could-not-open-source-file-gmmintrinh#comments http://software.intel.com/en-us/articles/catastrophic-error-could-not-open-source-file-gmmintrinh 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® Visual Fortran Compiler for Windows* 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 Program crashes or hangs on some systems
Reference Number : DPD200139120


Version : 
  • Intel® C++ & Visual Fortran Compilers for Windows* 11.1 initial release and update 1 release:
    • Intel® C++ & Visual Fortran Compiler for Windows* 11.1.035
    • Intel® C++ & Visual Fortran Compiler for Windows* 11.1.038
  • Intel® Parallel Studio
  • Intel® Parallel Composer initial release, and update 1 release


Operating System : 

Windows 7* or Windows Server 2008* R2


Problem Description : 

An issue with the Intel® Compiler's libirc*.* library may cause applications built against this library hang or a segmentation fault on the above operating systems.

 

You can determine the version number for your installation as follows.

  1. Open the build environment from [start->All Programs->Intel Software Development Tools->Intel C++ Compiler Professional 11.1.038->C++ Build Environment for Application running on IA32]
  2. run following command and the version number will be displayed:

>>icl

Intel(R) C++ Compiler Professional for applications running on IA-32, Version 11.1    Build 20090624 Package ID: w_cproc_p_11.1.038

Copyright (C) 1985-2009 Intel Corporation.  All rights reserved.

icl: command line error: no files specified; for help type "icl /help"
>>


Resolution Status : 

We are still running validation cycles on these configurations. We will update the Systems Requirements when we complete the validation cycle. We are proactively providing a solution to support our users who may encounter this issue.

  • For Intel® Compiler Professional Editions 11.1, this issue is resolved in update 11.1.048.
  • For Intel® Parallel Composer, this issue is resolved in the update 2 revised release. 

We've finished validation on Windows 7 and the above product updates or newer support Windows 7.

There is no work-around. 

Please do the following:

  1. Download the latest update from the Intel® Software Development Products Registration Center.
  2. Rebuild your application with the new compiler and libraries.




[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/program-crashes-or-hangs-on-some-systems Thu, 17 Sep 2009 12:59:11 -0700 http://software.intel.com/en-us/articles/program-crashes-or-hangs-on-some-systems#comments http://software.intel.com/en-us/articles/program-crashes-or-hangs-on-some-systems Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base The installation or uninstallation hangs at start-up dialog during &#34;Reading Existing Licenses&#34;
Reference Number : DPD200139120


Version : 
  • Intel®C++ & Visual Fortran Compilers 11.1 initial release and update 1 release:
    o Intel® C++ & Visual Fortran Compiler for Windows* 11.1.035
    o Intel® C++ & Visual Fortran Compiler for Windows* 11.1.038
  • Intel® Parallel Studio
  • Intel® Parallel Composer initial release, and update 1 release


Operating System : 
Windows 7* or Windows Server 2008* R2

Problem Description : 

We've seen several issues where the installation or uninstallation hangs on the Windows 7 OS.

When installing or uninstalling the above products on Windows 7 or Windows Server 2008 R2, you may see that the installation/uninstallation hangs at the following screen:

ReadingLic.JPG

The hang is caused by an issue in chklic.exe.

Resolution Status : 

We are still running validation cycles on these configurations. We will update the Systems Requirements when we complete the validation cycle. We are proactively providing a solution to support our users who may encounter this issue.  

This issue has been resolved:

  1. For Intel® Compiler Professional Editions 11.1, the fix is in the update 2 revised release 11.1.048.
  2. For Intel® Parallel Composer, the fix is in the update 2 revised release.

We've finished validation on Windows 7 and the above product updates or newer support Windows 7.

To download the latest update, log on to the Intel® Software Development Products Registration Center.

For uninstallation, you can work-around the issue by deleting the following file: 

<Install-dir>\setup_c\fli\chklic.exe



[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/the-installation-or-uninstallation-hangs-at-start-up-dialog-during-reading-existing-licenses Thu, 17 Sep 2009 12:58:09 -0700 http://software.intel.com/en-us/articles/the-installation-or-uninstallation-hangs-at-start-up-dialog-during-reading-existing-licenses#comments http://software.intel.com/en-us/articles/the-installation-or-uninstallation-hangs-at-start-up-dialog-during-reading-existing-licenses Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base __m128 data type incompatible with Microsoft definition
Code containing MS definition when compiled with Composer or icl will result in compilation errors because, the __m128 data type is defined as either a four packed single-precision floating-point values or one scalar single-precision number.  As a work-around, if you have code that uses MS definition of a union, then the file(s) containing such code will have to be compiled with MS compiler.

In the meantime, a feature request to support the union definition for compatibility with MS is in place, and this article will be updated as and when a release containing the support for MS compatibility is out in the very near future.

For any questions or further clarification on this incompatibility with MS, please feel free to post on any of the following forums:
         

http://software.intel.com/en-us/forums/intel-parallel-studio/

http://software.intel.com/en-us/forums/intel-c-compiler/


      
]]> http://software.intel.com/en-us/articles/m128-data-type-incompatible-with-microsoft-definition Tue, 08 Sep 2009 10:49:51 -0700 http://software.intel.com/en-us/articles/m128-data-type-incompatible-with-microsoft-definition#comments http://software.intel.com/en-us/articles/m128-data-type-incompatible-with-microsoft-definition Intel® Parallel Composer Intel® Compilers Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base delete operator causes an internal error
Reference Number : DPD200110776

Version : Intel(R) C++ Compiler for Windows version 11.0 or earlier
Operating System : Windows

Problem Description : 
When using "delete" operator in your template class methods, it confuses the compiler when you pass an array as template class parameter.

Sample.c:
template<class C>
class A
{
public:
	const C &operator*() const 
	{
		void *Ptr;
		delete (C*)Ptr;
		return *static_cast<C*>(Ptr); 
	}
};

class B 
{
public:
	B();
	virtual ~B();
};

B foo()
{
	A<B[1]> arr;
	return (*arr)[0];
}

Compiling output:

>>icl /c sample.cpp
Intel(R) C++ Compiler Professional for applications running on IA-32, Version 11.0    Build 20090318 Package ID: w_cproc_p_11.0.074
Copyright (C) 1985-2009 Intel Corporation.  All rights reserved.

sample.cpp
sample.cpp(8): warning #592: variable "Ptr" is used before its value is set
                delete (C*)Ptr;
                           ^
          detected during instantiation of "const C &A<C>::operator*() const [with C=B [1]]" at line 26

(0): internal error: backend signals

compilation aborted for sample.cpp (code 4)

 


Resolution Status : 
The above code does not follow the standard, but Microsoft* Visual C++ 2005* or 2008* can compile above code correctly and generates the correct "delete []". 

This incompatibility bug is fixed in the 11.1 version of the Intel C++ Compiler.


[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/delete-operator-causes-an-internal-error Fri, 21 Aug 2009 16:37:45 -0700 http://software.intel.com/en-us/articles/delete-operator-causes-an-internal-error#comments http://software.intel.com/en-us/articles/delete-operator-causes-an-internal-error Intel® C++ Compiler for Windows* 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