ld: symbol(s) not found when linking library containing no executable functions
If a library built with ar contains module data but no executable functions, the corresponding module symbols may not be resolved when an object referencing them is linked against the library. Author: Martyn Corden (Intel) Type: Known Issues |
11/05/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
|
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
|
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
|
Intel Debugger fails to install on Mac Pro with Quad-Core Intel Xeon 5500 series processor and Intel Xeon 3500 series processor
Intel(r) Debugger failed to install on Mac Pro with Quad-Core Intel Xeon 5500 series processor and Quad-Core Intel Xeon 3500 series processor Author: Qale (Intel) Type: Known Issues |
09/04/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® 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
|
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
|
Syntax error highlighting and "jump to" capabilities not functional under Xcode with Intel Fortran
Syntax error highlighting and "jump to" capabilities do not function under Xcode when using the Intel Fortran Compiler Professional Edition 11.0 release and corresponding Xcode integrations. Author: Kevin Davis (Intel) Type: Known Issues |
04/14/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
|
section not found for address 0x10000080C or address 0xFFFFFFFFFFFFFFFC on Intel 64 architecture Mac OS X 10.6
Intel compiler fails on Snow Leopard (Mac OS X 10.6) section not found for address 0x10000080C or 0xFFFFFFFFFFFFFFFC on Intel 64 architecture. Author: Qale (Intel) Type: Known Issues |
04/07/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® Fortran compiler - random number intrinsic function RAN malfunction
The Intel Fortran compiler elemental intrinsic function RAN will malfunction in the presence of a USE IFPORT statement. Author: Kevin Davis (Intel) Type: Known Issues |
03/09/2009
|
Fortran Xcode Build setting for Big/Little Endian file conversion causes unrecognized keyword compiler error
Selecting either Big Endian or Little Endian under the Intel Fortran Xcode Unformatted File Conversion configuration setting causes an unrecognized keyword compilation error. Author: Kevin Davis (Intel) Type: Known Issues |
03/08/2009
|
Library not found: crt0
Mac OS X linking error: libcrt0 not found. Author: Ronald W. Green (Intel) Type: Known Issues |
02/23/2009
|
library not found for -lcrt1.10.5.o
Problem : When user wants to create an executable targeted for Max OS X 10.4 system on a Mac OS X 10.5 system with 10.4u SDK there may be an error message in linkage stage:"ld: library not found for ... Author: Xiaoping Duan (Intel) Type: Known Issues |
02/09/2009
|
Intel® Fortran Compiler - Increased stack usage of 8.0 or higher compilers causes segmentation fault
The Intel Compilers have increased stack size needs in your application for performance analysis. This article describes how to increase stack size and/or workaround this problem by allocation on the heap (for Intel Fortran). Author: Wendy Doerner (Intel),Roland Wiele (Intel) Type: Known Issues |
02/05/2009
|
strip: bad n_sect for symbol table entry 7305
When trying to run strip on an executable generated with the 11.0 Intel(R) Compiler on Mac OS* using -openmp and -static-intel you get an error: strip: bad n_sect for symbol table entry 7305 Author: Wendy Doerner (Intel) Type: Known Issues |
01/14/2009
|
rel32 out of range linker error
linker error "call out of range" or "rel32 out of range" with 10.1 compiler on Mac OS* X Type: Known Issues |
01/13/2009
|
IDB Debugger Error When Reading Object Files
The IDB Debugger generates errors on Mac OS X when attempting to read object files. Author: Elizabeth S (Intel) Type: Known Issues |
01/09/2009
|
Error "variable not allocated" with assume realloc_lhs
If the "assume realloc_lhs" option and the "check pointer" option are used together, the error "Attempt to fetch from an allocatable variable when it is not allocated" may be incorrectly issued. Author: Steve Lionel (Intel) Type: Known Issues |
11/25/2008
|
