Intel® Visual Fortran Compiler for Windows* Knowledge Base

Submit New Article



Title Modified Date
The Server Threw An Exception From Visual Studio .Net 2003
An error message "The server threw an exception" is given when debugging after installing the Intel® Visual Fortran Compiler for Windows* 9.1.034 integrations into Visual Studio* .Net 2003.
Author: Elizabeth S (Intel)
Type: Software Defects
11/10/2009
Intel® Visual Fortran Compiler Documentation not available from Help menu in Visual Studio 2008 Shell*
Using Intel® Visual Fortran with Visual Studio 2008 Shell, the compiler documentation is not available from the Help menu.
Author: Elizabeth S (Intel),Roland Wiele (Intel)
Type: Software Defects
11/04/2009
Internal Compiler Error When Using IMSL Modules IMSL_LIBRARIES or LINEAR_OPERATORS for Intel 64
An internal compiler error may result when a program that USEs the IMSL* modules IMSL_LIBRARIES or LINEAR_OPERATORS is compiled by the Fortran compiler 11.1 for Intel(R) 64
Author: Steve Lionel (Intel)
Type: Software Defects
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: Software Defects
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: 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: Software Defects
10/05/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: Software Defects
09/24/2009
rc.exe not found-MS Visual Studio 2008 Shell
After performing an uninstall of the Intel Visual Fortran Compiler, subsequent attemps to build solutions using MS Visual Studio 2008 shell fail displaying the message 'rc.exe not found'
Author: Wendy Doerner (Intel),Roland Wiele (Intel)
Type: Software Defects
08/10/2009
Internal Compiler Error
What to do when a compilation results in an Internal Compiler Error, catastrophic error, internal abort, code 1 or code 3 error.
Author: Steve Lionel (Intel)
Type: Software Defects
07/02/2009
IMSL Install Fails with Remote Activated License
If you install Intel Visual Fortran Compiler Professional Edition with IMSL using Remote Activation for the license, the IMSL software will not install using the activated license.
Author: Steve Lionel (Intel)
Type: Software Defects
05/29/2009
Intel® Premier support frequently asked questions
This Intel® Premier Support FAQ describes what it is, who is eligible, how to obtain a login ID, how to submit issues and how to get product updates.
Author: Chuck (Intel)
Type: Software Defects
05/21/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: Software Defects
05/18/2009
Cannot WRITE to window created with AllocConsole
If a non-console application creates a console window by calling AllocConsole, Fortran code cannot write to the console.
Author: Steve Lionel (Intel)
Type: Software Defects
05/07/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: Software Defects
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: Software Defects
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: Software Defects
03/20/2009
Linker Cannot Find Application Entry Point
Trailing backslash when additional libraries are specified in IDE project properties or using LIBPATH linker option causes xilink to report that entry point must be defined.
Author: Elizabeth S (Intel)
Type: Software Defects
03/06/2009
Cachesize intrinsic doesn't work for Intel Core I7 processor
The cachesize() intrinsic function returns an incorrect value for the Intel(R) Core(TM) i7 processor
Author: Martyn Corden (Intel)
Type: Software Defects
02/04/2009
Visual Studio 'Link Library Dependencies' for Intel Fortran and C++
The Visual Studio Linker (or Librarian) General property 'Link Library Dependencies' is now available for Windows Visual Fortran and C++ Compiler 11.0 projects.
Author: Patrick Kennedy (Intel)
Type: Software Defects
01/28/2009
FLUSH on unopened file gives error 707
If a Fortran FLUSH statement is executed for a unit that is not open, a run-time error 707 occurs.
Author: Steve Lionel (Intel)
Type: Software Defects
01/15/2009
Use Intel Compiler to build 64-bit code with Windows SDK for Server 2008
Intel Compiler version 10.1 doesn't support Windows SDK for Server 2008. 11.0.061 and 066 update does not set the 64-bit build environment correctly. This article provide a workaround for this issue.
Author: Hao Jiang (Intel)
Type: Software Defects
01/05/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: Software Defects
11/25/2008
Compiler 11.0 OpenMP programs exhibit high core usage
Compiler 11.0 C++ and Fortran OpenMP-enabled programs on Windows, Linux, and Mac OS X have high CPU utilization for all cores in a multi-core system, even if it is known that not all cores are being fully utilized. Setting KMP_BLOCKTIME has no effect.
Author: pbkenned
Type: Software Defects
11/20/2008
Fortran intrinsic module errors when linked to DLL libraries
Intel Fortran applications using derived type constants from intrinsic modules, such as C_NULL_PTR from ISO_C_BINDING, may execute incorrectly or fail to link when linked against the DLL form of the Fortran run-time libraries.
Author: Steve Lionel (Intel)
Type: Software Defects
10/15/2008
Intel Fortran Compiler - FTELL problem with buffered I/O
If a Fortran unit is opened for buffered I/O, the FTELL and FTELLI8 RTL functions do not take account of data that is still in the buffer.
Author: Martyn Corden (Intel)
Type: Software Defects
09/26/2008