BIND(C) does not work for COMPLEX
A COMPLEX Fortran function built with the BIND(C) attribute does not follow the x64 ABI and is not interoperable with the Intel C compiler or with gcc. Author: Martyn Corden (Intel) Type: Software Defects |
11/20/2009
|
dyld:Library not loaded:libiomp5.dylib
when use intergarated MKL or IPP from Intel pro compiler, the error dyld:Library not loaded:libiomp5.dylib show. Add rigth environment variable can solve the probelm Author: Ying H (Intel) Type: Errors and Diagnostics |
11/16/2009
|
Which version of Intel IPP, Intel MKL and Intel TBB is installed by the Intel® Compiler Professional Edition?
The page lists the Intel IPP, Intel MKL and Intel TBB versions installed by the Intel® Compiler Professional Edition. Author: AmandaS (Intel) Type: Installation,Compatibility |
11/06/2009
|
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,Software Defects |
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 for Linux* - Invoking the compiler
For 11.x compilers (10.x compilers did not need an argument), enter:
$ source <path-to-ifort-bin-dir>/ifortvars.sh (bash) <arg>
% source <path-to-ifort-bin-dir>/ifortvars. ... Author: Wendy Doerner (Intel) Type: Tips and Techniques,Technical Notes |
11/04/2009
|
Being Successful with the Intel® Compilers -- You Need to Know
Tips and techniques on using the Intel Compilers to maximize your application performance. Author: Brandon Hewitt (Intel),Vangal Venkatesh Type: Tips and Techniques,Performance and Optimization |
11/02/2009
|
Fortran READ returns iostat=98 error
Fortran READ statement can return an out of memory error if there is not enough virtual memeory. Author: Elizabeth S (Intel) Type: Errors and Diagnostics |
10/30/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: Installation,Known Issues,Software Defects,Compatibility,Technical Notes |
10/22/2009
|
Diagnostic 5656: Variable xxxx too large for NTCOFF. Bigger than 2GB. Use heap instead
2 GByte limit on static and data areas in COFF object file format. Author: Steve D. (Intel) Type: Errors and Diagnostics |
10/19/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,Software Defects |
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,Software Defects |
10/05/2009
|
Intel® FLEXlm* license servers
Links to the various FLEXlm* license servers used for managing floating licenses for Intel(R) Compilers. Author: Chuck (Intel) Type: Installation |
10/02/2009
|
Development Products Download, Registration and Licensing Help
Help Yourself: Knowledge Base - The best place to find answers to your questions Intel® Software Development Products Registration Center - Register a product, see the products you have regist ... Author: Kristen (Intel) Type: Download, Registration, Licensing |
09/25/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
|
Consistency of Floating-Point Results using the Intel® Compiler
Why doesn’t my application always give the same answer?
Tradeoffs between floating-point accuracy, reproducibility and performance are discussed with examples;recommendations are made for improving reproducibility while limiting the impact on performance Author: Martyn Corden (Intel) |
09/18/2009
|
Diagnostic 11003: no IR in object file xxxx; was the source file compiled with xxxx
You are attempting to link an object file that was not compiled with IPO in and IPO build.
Author: Mark Sabahi (Intel) Type: Errors and Diagnostics |
09/16/2009
|
Diagnostic 6502: COMMON cannot be extended beyond the beginning of a block.
Description of Fortran error 6502: COMMON cannot be extended beyond the beginning of a block Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
09/11/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: Installation,Known Issues,Software Defects |
09/04/2009
|
Diagnostic 6405: The same named entity from different modules and/or program units cannot be referenced.
Information about Fortran diagnostic (error) 6405: The same named entity from different modules and/or program units cannot be referenced. Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/31/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,Errors and Diagnostics |
08/31/2009
|
Tips for using PARDISO
Provides tips for getting started and corrects some of the common mistakes made by first-time and experienced users. Author: Gennady Fedorov (Intel),Todd Rosenquist (Intel) Type: Tips and Techniques |
08/28/2009
|
Diagnostic 8068: If the language-binding-spec has a NAME= specifier
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8069: This symbol has multiple BIND statement/attribute declarations which is not allowed.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8070: The ASYNCHRONOUS= specifier in a data transfer statement must be a character initialization expression (Constraint C924).
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
