Error : Failed to enable trusted storage check for licensing
"error #10310: Failed to enable trusted storage check for licensing: Warning" Enable Trusted Storage failed (flexnet error code 20). Trusted Storage based licence could " is a known issue. The workaround for the issue is to set the library paths. Author: Shamla (Intel) Type: Known Issues |
11/10/2009
|
Intel® Professional Edition Compilers 11.1 Fixes List
This page lists fixes that have been made in Intel Professional Edition Compilers 11.1. Author: Elizabeth S (Intel),Roland Wiele (Intel) Type: Known Issues |
11/05/2009
|
Build CP2K using Intel Fortran compiler Professional Edition
This article show how to build CP2K for Intel64 platform, using Intel Fortran compiler Professional Edition version 11.0.083 / 11.1.059, and Intel Math Kernel Library (MKL) with FFTW 3.x support Author: Hao Jiang (Intel) Type: Known Issues |
11/03/2009
|
Intel Fortran Compiler 11.1 Release Notes
Current release notes and installation guide for the Intel Fortran Compiler 11.1 products for Linux, Mac OS X and Windows Author: Steve Lionel (Intel) Type: Known Issues |
10/22/2009
|
Incorrect padding added for SEQUENCE or BIND(C) type with UNION
Describes a Fortran compiler defect where padding is inappropriately added inside a UNION in a SEQUENCE or BIND(C) derived type Author: Steve Lionel (Intel) Type: Known Issues |
10/16/2009
|
Putting -lm Before User Objects/Libraries on Link Line Can Impact Performance
Recommended linking model:
icc/icpc/ifort [user objs] [user libs] [sys libs]
Using -lm (the GNU math library) prior to user-created objects or libraries causes the GNU libm to be used instead of the Intel math library, impacting performance. Author: Brandon Hewitt (Intel) Type: Known Issues |
10/14/2009
|
Run-Time Error 408 when optional character argument omitted
Description of a compiler defect which causes an inappropriate error 408 to be issued at run-time when bounds checking is enabled and an optional character argument is omitted in a call to a routine. Author: Steve Lionel (Intel) Type: Known Issues |
10/05/2009
|
Catastrophic error: could not open source file "gmmintrin.h"
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 W ... Author: Jennifer Jiang (Intel) Type: Known Issues |
09/25/2009
|
Thread affinity compiler switches have no effect
Thread affinity compiler switches /Qpar-affinity (Windows*) or -par-affinity (Linux*) have no effect when the executable is run. Author: Patrick Kennedy (Intel) Type: Known Issues |
09/24/2009
|
Error 6405 with interface checking and EXTERNAL declaration in module
Reference Number : DPD200139304Version : 11.1Operating System : AllProblem Description : The compiler will incorrectly issue diagnostic 6405: The same named entity from different modules and/or progr ... Author: Steve Lionel (Intel) Type: Known Issues |
08/31/2009
|
Intel® compiler error #10236 issued when using -soname corrupts resulting shared library on Linux
Intel® Linux compilers issue compiler error #10236 and create invalid shared library when using -Xlinker with -soname Author: Kevin Davis (Intel) Type: Known Issues |
08/21/2009
|
Intel® Fortran and C++ compilers – Invalid option -i turns on incremental linking on Linux
Both the Intel® Fortran and C++ compilers for Mac OS and Linux quietly ignore the unknown option "-i" and pass it to the linker. Author: Kevin Davis (Intel) Type: Known Issues |
08/13/2009
|
Intel® Fortran compiler – Option -extend-source not ignored for .F90 source files
Intel Fotran 11.x compiler does not properly ignore option -extend-source for .F90 source files Author: Kevin Davis (Intel) Type: Known Issues |
08/04/2009
|
Installing Intel Compilers on OpenSUSE
How to install the Intel Compilers on OpenSUSE 11.2 Author: Ronald W. Green (Intel) Type: Known Issues |
07/22/2009
|
idb cannot print USEd mod variables
Problem :-- Debugger does not print the use-associated variablesmodule modinteger :: i, j, k, lcontains subroutine initi = 1j = 2k = 3l = 4end subroutine initend module moduse modcall initprint *, i, j ... Author: Milind Kulkarni (Intel) Type: Known Issues |
07/14/2009
|
ifort 2GB Record Memory Limit Bug on Itanium and Intel 64
reading/writing files in large chunks (>2GB) may truncate to 2 GB on Linux distros using kernel 2.6.16 or later. Author: Roland Wiele (Intel) Type: Known Issues |
07/02/2009
|
Intel Visual Fortran Pro for Linux Notes On gprof Use
Notes on using gprof with Intel Fortran Compiler Pro for Linux Author: Ronald W. Green (Intel) Type: Known Issues |
07/01/2009
|
Compiler installation path changed for Intel® Cluster Toolkit Compiler Edition 3.2.1
Intel® Cluster Toolkit Compiler Edition 3.2.1 or later installs the 11.x compiler components in different directories compared to earlier products. The compiler components in the toolkit now use the same layout as the standalone 11.x compiler products. Author: Patrick Kennedy (Intel) Type: Known Issues |
06/22/2009
|
'mpiexec -idb' fails to start the Intel GUI debugger correctly
If you use Intel MPI 3.0 or later, the 11.x Intel debugger (IDB) GUI fails to start correctly if launched via mpiexec. Doing 'mpiexec -idb ...' will bring up the GUI and an IDB console, but neither can be used to debug the MPI application. Author: Patrick Kennedy (Intel) Type: Known Issues |
06/17/2009
|
Syntax error for array constructor with datatype keyword value
A syntax error is given for array constructors of the form (/name/) where name is a PARAMETER constant that has the same name as a datatype keyword. Author: Steve Lionel (Intel) Type: Known Issues |
05/18/2009
|
Boxed Product Packages NOT Updated All
This article describes some boxed product packages have not been updated to what they look like in Intel(R) Business Exchange web site, etc. Author: Lina Liu (Intel) Type: Known Issues |
05/15/2009
|
Error #5508 Declaration of routine conflicts with a previous declaration
If enable /warn:interfaces /gen-interfaces with Intel FORTRAN compiler 11.0.074 for Windows, 11.0.083 for Linux, you will see error message Declaration of routine conflicts with a previous declaration. This article gives a workaround for this issue. Author: Hao Jiang (Intel) Type: Known Issues |
04/15/2009
|
Multiple definitions of floating-point exception parameters such as FPE_M_TRAP_OVF
Referencing parameters related to floating-point exceptions via the IFLPORT or IFCORE and IFPORT modules may give errors such as
error #6405: The same named entity from different modules and/or program units cannot be referenced. [FPE_M_TRAP_DIV0] Author: Martyn Corden (Intel) Type: Known Issues |
04/08/2009
|
Fortran RESHAPE in type declaration causes internal compiler error
Fortran RESHAPE intrinsic usage in a type declaration statement with an mismatched result array shape specification causes an internal compiler error. Author: Kevin Davis (Intel) Type: Known Issues |
03/20/2009
|
Intel® Debugger (IDB) for Linux - Error: Assertion failed involving getThreadId()
The Intel Debugger for Linux version 11.0 suffers an Assertion failed error involving getThreadId() when loading an executable. Author: Kevin Davis (Intel) Type: Known Issues |
03/09/2009
|
