Intel Software Network articles feed

Intel® Parallel Composer Fixes List

Wed, 04 Nov 2009 09:32:39 -0800

NOTE: Defects and feature requests described below represent specific issues with specific test cases. It is difficult to succinctly describe an issue and how it impacted the specific test case. Some of the issues listed may impact multiple architectures, operating systems, and/or languages. If you have any questions about the issues discussed in this report, please post on the user forums, http://software.intel.com/en-us/forums.

Update 3 (Posted November 2009)

DPD200012215 C, C++ Documentation about application register access in user manual is vague
DPD200110916 C++ VC compatibility issue on allowing pure virtual specifiers in prototype instantiations
DPD200136502 C++ unable to obtain mapped memory
DPD200136749 C, C++ Switch to fixed address memory mapping by default for PCH
DPD200136996 C++ (0): internal error: backend signals
DPD200136996 C++ (0): internal error: backend signals
DPD200137318 C, C++ /Qprof-psa-* options should be removed from /help
DPD200139432 C, C++ "internal error: 0_1149" when using /fp:fast
DPD200139624 C++ (0): internal error: backend signals in termination test in openmp iterator loop
DPD200140317 C Wrong output when vectorizing
DPD200140450 C++ problem with debug info of enum bit-fields with pch (internal error: 0_45080)
DPD200140550 C Internal compiler error in PCG

The Intel® IPP Library 6.1 Fixes List can be found here

Update 2 Revised (Posted October 2009)

DPD200139120 C, C++ - Update 2 list below has more details on this issue. Note: The package was 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)

DPD200139120 C,C++ - Composer may hang or encounter a segmentation-fault when run on Microsoft* Windows 7* or
Windows Server 2008* R2. Please refer to the following links for more details:

1) The installation or uninstallation hangs at start up dialog during reading existing licenses
2) Program crashes or hangs on some systems

DPD200003663 C,C++ - Access mechanism inconsistency for #pragma section()/__declspec(allocate()) generated symbols

DPD200040394 C++     - Split blocks at GP reload to improve debug order

DPD200042107 C,C++ - Proton compile time 100x of MS VC++ 7.0 due to long constant propagation time

DPD200051151 C,C++ - FLEXlm server fails to start on Windows Server 2008 x64 architecture

DPD200084262 C          - stack run time check reports failure for 64byte alignment

DPD200111309 C,C++ - Need consistent correspondence between OMP hread ids and global thread ids in non-nested code

DPD200111314 C,C++ - Error initializing foreign thread's OMP affinity mask

DPD200120952 C++     - OpenMP task crashes with new class statement in Debug mode

DPD200121133 C          - Problem caused by "Hoist Optimize Branches" with -O2 and -O3

DPD200135696 C          - unresolved symbol with /Qipo in 11.x only - 10.x works

DPD200135966 C++      - icc warning level (/W4) is incompatible with vc warning level

DPD200136540 C          - runtime crash when /Qnum-opt = 25

DPD200136776 C,C++ -  "(0): internal error: 0_0" with multi-source compilation

DPD200136951 C++     - 0x5C Japanese Character resulting in garbled output

DPD200137318 C,C++ - /Qprof-psa-* options should be removed from /help

DPD200137781 C++     - Need scalar variable privatization support for std::complex data type with function call

DPD200138343 C,C++ - "(0) internal error: backend signals" with openmp on "while"

DPD200138609 C++     - Compiler fails to select correct template function for passed arguments

DPD200139006 C++     - Error during project conversion with Intel C++ compiler in VS2008

DPD200139120 C,C++ - Application hangs due to xgetbv in __intel_cpu_indicator_init() function

Update 1 (Posted July 2009)

DPD200121459 - "Taskwaits" window of the Intel Parallel Debugger Extension not work

DPD200120676 - setting "Interprocedural Optimization" to "Disable (/qnoipo)" under property "Linker > Optimization" not working

DPD200112207 - memory leak using Parallel Debugger Extension on Thread Data Sharing Events

DPD200111854 - Environment macros are ignored in property sheets user macros.

DPD200121009 - icl driver handles -EHc- (turn off extern C) switch incorrectly

DPD200136451 - allowing namespace::classname redeclaration

DPD200136607 - internal error when creating a thunk for vector delete on Windows

DPD200136717 - -O2 causes unresolved symbol "___tmainCRTStartup"

DPD200135694 - problem with template argument deduction when unviable abstract base class type parameters are instantiated

DPD200032028 - missing many opportunities to break false dependences

DPD200039735 - compiler fails to specialize function template

DPD200040035 - preprocessor unable to process macro definition

DPD200118328 - explicit overriding of the virtual methods causes wrong results

DPD200119382 - loop was not vectorized: reduction property lost in IVS

DPD200119841 - /RTC1 does not mapped to /RTCsu

DPD200120035 - kmp_set_defaults() isn't working

DPD200120115 - Resource leak in libiomp5mt.lib

DPD200135887 - IDE integration can not launch c:\windows\system32\cmd.exe on a dual-boot system

DPD200136041 - Visual C++ 2008 and later allow virtual override when parameters differ in const/volatile qualilfication

DPD200135511 - /Zi with /Yu generates undefined symbols from Boost* header variables

Compiler issues the message "Catastrophic error: unable to obtain mapped memory (see pch_diag.txt) "

Thu, 22 Oct 2009 17:00:28 -0700

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

Warning #677: memory usage conflict with precompiled header file seen on Windows* XP and Linux*

Thu, 22 Oct 2009 15:35:39 -0700

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

Program crashes or hangs on some systems

Thu, 17 Sep 2009 12:59:11 -0700

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.

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

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:

Download the latest update from the Intel® Software Development Products Registration Center.
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.]

The installation or uninstallation hangs at start-up dialog during "Reading Existing Licenses"

Thu, 17 Sep 2009 12:58:09 -0700

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:

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

Resolution Status :

This issue has been resolved:

For Intel® Compiler Professional Editions 11.1, the fix is in the update 2 revised release 11.1.048.
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:

\setup_c\fli\chklic.exe

__m128 data type incompatible with Microsoft definition

Tue, 08 Sep 2009 10:49:51 -0700

The __m128 data type as defined in xmmintrin.h for use with the Streaming SIMD Extensions instructions intrinsics is defined as a union in Microsoft (MS) header, while it is supported as a struct in the Intel® Parallel Composer or Intel® C++ Compiler for Windows* (icl) resulting in incompatibility with MS.

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/

Stack Frame Run-time Check incompatible with Microsoft* Visual C++ x64

Sun, 02 Aug 2009 20:03:08 -0700

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

Use of PCH and /Zi with Boost* Libraries May Result in unresolved external symbols due to Anonymous Namespace Use

Thu, 23 Jul 2009 22:06:41 -0700

Reference Number : DPD200135511

Version : 11.1

Operating System : Windows*

Problem Description : The Boost* STL library's bind functionality uses a construct called placeholders to bind function arguments to a function. Boost implements these placeholders in an anonymous namespace which the Intel® C++ Compiler has problems with when pre-compiled header files are used and debug symbol generation is enabled. The following code demonstrates the problem (requires Boost* libraries).

pch.h:

#include

pch.cpp:

#include "pch.h"

test-bind.cpp:

#include "pch.h" class blh_widge { public: void Init(); private: void OnInputComplete(int, int, int); }; void blh_widge::Init() { boost::bind(&blh_widge::OnInputComplete, this, _1, _2, _3) {} } int main() { return(0); }

Reproduce:

icl -Od -I -Ycpch.h -Fptest-bind.pch -c -Zi pch.cpp icl -Od -I -Yupch.h -Fptest-bind.pch -Zi test-bind.cpp test-bind.cpp Microsoft (R) Incremental Linker Version 8.00.50727.762 Copyright (C) Microsoft Corporation. All rights reserved. -out:test-bind.exe -debug -pdb:test-bind.pdb test-bind.obj test-bind.obj : error LNK2019: unresolved external symbol "struct boost::arg<1> __N_13_test_bind_cpp_main::_1" (?_1@__N_13_test_bind_cpp_main@@3U?$arg@$00@boost @@A) referenced in function ___sti__?_1@__N_13_test_bind_cpp_main@@3U?$arg@$00@b oost@@A test-bind.obj : error LNK2019: unresolved external symbol "struct boost::arg<2> __N_13_test_bind_cpp_main::_2" (?_2@__N_13_test_bind_cpp_main@@3U?$arg@$01@boost @@A) referenced in function ___sti__?_2@__N_13_test_bind_cpp_main@@3U?$arg@$01@b oost@@A test-bind.obj : error LNK2019: unresolved external symbol "struct boost::arg<3> __N_13_test_bind_cpp_main::_3" (?_3@__N_13_test_bind_cpp_main@@3U?$arg@$02@boost @@A) referenced in function ___sti__?_3@__N_13_test_bind_cpp_main@@3U?$arg@$02@b oost@@A test-bind.exe : fatal error LNK1120: 3 unresolved externals

Resolution Status : This issue is resolved in the Intel® Parallel Composer Update 1 or Intel® C++ Compiler Professional Edition for Windows* 11.1.038.

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

compiler internal error 0_1279

Mon, 20 Jul 2009 19:50:24 -0700

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

IDE Integration with Microsoft Visual Studio* 2008 Doesn't Install When Windows* SDK for Windows* Server 2008 is Installed

Mon, 13 Jul 2009 10:00:29 -0700

Problem : The integration into Microsoft Visual Studio* 2008 does not install. There is no error message during installation, but you will not find any toolbar or compiler-related entries specific to the Intel® C++ Compiler or Intel® Parallel Composer.

Environment : Microsoft Visual Studio* 2008

Root Cause : Installing the Windows* SDK for Windows* Server 2008 and .NET Framework 3.5 breaks environment scripts as described here†. These scripts are used by the installation when integrating into the Microsoft Visual Studio* IDE and when broken as described will silently prevent the installation from working.

Resolution : Use the workaround provided in this article† to correct the problem and then reinstall the IDE integration.

† This link will take you off of the Intel Web Site. Intel does not control the content of the destination Web Site.