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: Known Issues |
11/10/2009
|
IDE integration missing when installing the 10.x release over an 11.x release
In some cases uninstalling the 11.x compiler and then installing a 10.x compiler, will appear to still show the 11.1 integration (and not show the 10.x integration) in Microsoft* Visual Studio. Remove the install directory to workaround the problem. Author: Wendy Doerner (Intel) Type: Known Issues |
11/09/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® 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: Known Issues |
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: Known Issues |
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: 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
|
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
|
Program crashes or hangs on some systems
Reference Number : DPD200139120Version :
Intel® C++ & Visual Fortran Compilers for Windows* 11.1 initial release and update 1 release:
Intel® C++ & Visual Fortran Compiler for Windows ... Author: Jennifer Jiang (Intel) Type: Known Issues |
09/17/2009
|
The installation or uninstallation hangs at start-up dialog during "Reading Existing Licenses"
Reference Number : DPD200139120Version :
Intel®C++ & Visual Fortran Compilers 11.1 initial release and update 1 release: o Intel® C++ & Visual Fortran Compiler for Windows* 11.1.035o In ... Author: Jennifer Jiang (Intel) Type: Known Issues |
09/17/2009
|
Parallel Debugger Extension Exceptions: 0xa1a01db1, 0xa1a01db2
When run under the VS2005 debugger, code compiled with Qopenmp display exceptions:
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB1: 0xa1a01db1.
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB2: 0xa1a01db2.
Author: Roland Wiele (Intel) Type: Known Issues |
09/08/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
|
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: Known Issues |
08/10/2009
|
Duplicate Fortran Project Templates in Visual Studio 2005
Installing Intel Visual Fortran with Visual Studio 2005 Premier Partner Edition over a Japanese language Visual Studio 2005 can cause Fortran project items to be duplicated. Author: Steve Lionel (Intel) Type: Known Issues |
08/04/2009
|
Can not find Intel Fortran in New Project Menu
After install Intel Visual Fortran compiler in non-English Windows*, may not able to see Intel Fortran item in New Project menu. The workaround is to change the "Language for non-Unicode program" setting and do Visual Studio integration again. Author: Hao Jiang (Intel) Type: Known Issues |
06/18/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: Known Issues |
05/29/2009
|
Can I export a makefile from Visual Studio?
The capability to export makefiles from Visual Studio is not available. Author: Steve D. (Intel) Type: Known Issues |
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: 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
|
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: Known Issues |
05/07/2009
|
64-bit remote debugger is not automatically installed on 64-bit Windows
This article discuss a known issue as some version of Intel Visual Fortran compiler 10.1 and 11.0 can not install the 64-bit remote debugger automatically. We introduced the root cause and workaround, and the latest fix status for this issue. Author: Hao Jiang (Intel) Type: Known Issues |
05/06/2009
|
Error: IMSL Installation Failure with Unlock Code of Remote Activation
When customers use the remote activation option to install IMSL, the error window will be popped up where shows The response entered is incorrect. This article helps customers who get this error out to proceed to install IMSL successfully. Author: Lina Liu (Intel) Type: Known Issues |
04/24/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
|
