• English

• English

• English

• English

• English
• Japanese

• English

• English
• Japanese

If you wish to install the redistributable package "silently", so that no output is presented to the user, run the executable with the following options added to the command line like:
>> w_cproc_p_11.1.04x_redist_xxx.exe /S /V/qn

Links to the redistributable packages

Intel C++ Compiler for Windows 11.1.048 (update 2 revised) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64	Intel Visual Fortran Compiler for Windows 11.1.048 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64
Intel C++ Compiler for Windows 11.1.051 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64	Intel Visual Fortran Compiler for Windows 11.1.051 (update 3) • Redistributable library package for IA32 • Redistributable library package for Intel 64 • Redistributable library package for IA-64

References

Redistribution of Application Binaries Built for Microsoft* Windows

The Intel Fortran compiler supports many features that are new to the latest revision of the Fortran standard, Fortran 2003 (ISO/IEC 1539:2004 ). Additional Fortran 2003 features will appear in future versions. Fortran 2003 features supported by the version 11.1 compiler include:

• The Fortran character set has been extended to contain the 8-bit ASCII characters ~ [ ] ` ^ { } | # @
• Names of length up to 63 characters
• Statements of up to 256 lines
• Square brackets [ ] are permitted to delimit array constructors instead of (/ /)
• Structure constructors with component names and default initialization
• Array constructors with type and character length specifications
• A named PARAMETER constant may be part of a complex constant
• Enumerators
• Allocatable components of derived types
• Allocatable scalar variables
• Deferred-length character entities
• PUBLIC types with PRIVATE components and PRIVATE types with PUBLIC components
• ERRMSG keyword for ALLOCATE and DEALLOCATE
• SOURCE= keyword for ALLOCATE
• Type extension
• CLASS declaration
• Polymorphic entities
• Inheritance association
• Deferred bindings and abstract types
• Type-bound procedures
• TYPE CONTAINS declaration
• ABSTRACT attribute
• DEFERRED attribute
• NON_OVERRIDABLE attribute
• ASYNCHRONOUS attribute and statement
• BIND(C) attribute and statement
• PROTECTED attribute and statement
• VALUE attribute and statement
• VOLATILE attribute and statement
• INTENT attribute for pointer objects
• Reallocation of allocatable variables on the left hand side of an assignment statement when the right hand side differs in shape or length (requires option "assume realloc_lhs")
• ASSOCIATE construct
• SELECT TYPE construct
• In all I/O statements, the following numeric values can be of any kind: UNIT=, IOSTAT=
• NAMELIST I/O is permitted on an internal file
• Restrictions on entities in a NAMELIST group are relaxed
• FLUSH statement
• WAIT statement
• ACCESS='STREAM' keyword for OPEN
• ASYNCHRONOUS keyword for OPEN and data transfer statements
• ID keyword for INQUIRE and data transfer statements
• POS keyword for data transfer statements
• PENDING keyword for INQUIRE
• The following OPEN numeric values can be of any kind: RECL=
• The following READ and WRITE numeric values can be of any kind: REC=, SIZE=
• The following INQUIRE numeric values can be of any kind: NEXTREC=, NUMBER=, RECL=, SIZE=
• Recursive I/O is allowed in the case where the new I/O being started is internal I/O that does not modify any internal file other than its own
• IEEE Infinities and NaNs are displayed by formatted output as specified by Fortran 2003
• BLANK, DELIM, ENCODING, IOMSG, PAD, ROUND, SIGN, SIZE I/O keywords
• DC, DP, RD, RC, RN, RP, RU, RZ format edit descriptors
• In an I/O format, the comma after a P edit descriptor is optional when followed by a repeat specifier
• Rename of user-defined operators in USE
• INTRINSIC and NON_INTRINSIC keywords in USE
• IMPORT statement
• Allocatable dummy arguments
• Allocatable function results
• PROCEDURE declaration
• Procedure pointers
• ABSTRACT INTERFACE
• PASS and NOPASS attributes
• Execution of a STOP statement displays a warning if an IEEE floating point exception is signaling
• The COUNT_RATE argument to the SYSTEM_CLOCK intrinsic may be a REAL of any kind
• COMMAND_ARGUMENT_COUNT intrinsic
• GET_COMMAND intrinsic
• GET_COMMAND_ARGUMENT intrinsic
• GET_ENVIRONMENT_VARIABLE intrinsic
• IS_IOSTAT_ END intrinsic
• IS_IOSTAT_EOR intrinsic
• MAX/MIN/MAXVAL/MINVAL/MAXLOC/MINLOC intrinsics allow CHARACTER arguments
• MAXLOC or MINLOC of a zero-sized array returns zero (requires option "assume noold_maxminloc")
• MOVE_ALLOC intrinsic
• NEW_LINE intrinsic
• SELECTED_CHAR_KIND intrinsic
• The following intrinsics take an optional KIND= argument: ACHAR, COUNT, IACHAR, ICHAR, INDEX, LBOUND, LEN, LEN_TRIM, MAXLOC, MINLOC, SCAN, SHAPE, SIZE, UBOUND, VERIFY
• Type inquiry intrinsic functions
• ISO_C_BINDING intrinsic module
• IEEE_EXCEPTIONS, IEEE_ARITHMETIC and IEEE_FEATURES intrinsic modules
• ISO_FORTRAN_ENV intrinsic module

Please see the compiler release notes for an updated list.

The Intel Fortran compiler also supports some features from the draft Fortran 2008 standard. These include:

• Passing internal procedures as actual arguments
• A procedure pointer can point to an internal procedure
• In ALLOCATE, if source-object does not have a shape specified, the shape is taken from the SOURCE= argument

Intel Fortran also includes a number of extensions to Fortran 2003, as well as command-line options that allow you to override the default actions of the compiler.

In some cases, the default behavior of the Intel Fortran Compiler does not conform to Fortran 2003 semantics.  The following table lists the compiler options which are not enabled by default and which must be specified to obtain full Fortran 2003 semantics. Note that, in some cases, enabling these options may lower run-time performance.

For more information, please refer to the "Compiler Options" section of the Intel Fortran Compiler documentation.

For Fortran applications built within Microsoft Visual Studio*, you can debug the program by setting a breakpoint at the first executable line and then pressing F5 (or clicking the GO button).  But if you built the application using command line tools, this method is not available.  This article describes how to begin debugging an application built from the command line.

Note: This technique requires that a supported version of Microsoft Visual Studio is installed. It will not work if you are using Microsoft Visual C++ Express Edition* or the Windows Platform SDK to support the compiler environment.

Building the Application

Add the /debug option to the ifort command when compiling and linking.  For example:

ifort /debug /Od hello.f90

or

ifort /c /debug /Od main.f90
ifort /c /debug /Od sub.f90
ifort /debug /exe:main.exe main.obj sub.obj

This will create a .pdb (Program Database) file alongside the executable.  The .pdb file is required for debugging. The /Od option disables optimization to enhance debugging.

Start Debugging

In order to start the debugger, you must be in a command prompt environment which includes definitions for Microsoft Visual Studio.  This is the default for an Intel Fortran "Build Environment" session.

Type the command:

devenv /debugexe hello.exe

where hello.exe is replaced with the name of your executable. If the program requires command line arguments, they may follow the executable name on the command line.

Wait for Visual Studio to finish loading.

You must now set a breakpoint at the main program.  To do this, select Debug > New Breakpoint > Break at Function... or press CTRL-B.  You will see a dialog similar to the following:

If you have built an IA-32 architecture application, type into the Function box the name:

_MAIN__

Note that there is one underscore before MAIN and two underscores after.

If you have built an Intel® 64 architecture application, type into the Function box the name:

MAIN__

In this case there is no leading underscore and two trailing underscores.

Click OK.

Press F5 or click the Start Debugging button.  The program will now begin executing but will break at the Fortran main program.  From there you may set additional breakpoints as desired.

If at the end of the session you close Visual Studio and allow it to save the new Visual Studio solution it created, you can debug again just by opening the solution (.sln file).  Your previously set breakpoints will be preserved.

Questions?

If you have comments or questions specifically relating to this article, use the Comments box below. For other questions, please visit our user forum.

This article explains how to install, configure and use the IMSL* Fortran Numerical Library, as provided with Intel® Visual Fortran Professional Edition with IMSL*, version 11. It is not applicable to versions of IMSL obtained from other sources.

This article supplements the on-disk documentation provided at Building Applications > Using Libraries > Using the IMSL* Mathematical and Statistics Libraries. Please refer to that text for more detail on using IMSL.

The IMSL* libraries are supplied on a second DVD in boxed products and as separate downloads from the Intel Software Development Products Registration Center. There are three installation files, one for each target architecture. The file names are of the form:

• w_cprofimsl_p_11.0.xxx_ia32.exe - for building applications that run on IA-32
• w_cprofimsl_p_11.0.xxx_intel64.exe - for building applications that run in Intel® 64
• w_cprofimsl_p_11.0.xxx_ia64.exe - for building applications that run on IA-64

You must install the Intel Visual Fortran compiler before installing the IMSL libraries. If you will be developing applications to run on more than one architecture, we recommend that you install the IMSL package for your development computer's architecture last.

Intel Visual Fortran 11.0.061 and 11.0.066 does not automatically establish the IMSL environment when the command line Build Environment scripts are run. Until this is corrected in a future update, you will have to edit the compiler .bat files manually to also set the IMSL environment.

For the IA-32 architecture target, open the file

C:\Program Files\Intel\Compiler\11.0\066\fortran\Bin\IA32\ifortvars_IA32.bat

in Notepad or another text editor. Add the following line at the end of the file:

Make sure that the added text is contained on one line only.

For the Intel 64 architecture target, the file to edit is

...\Intel64\ifortvars_intel64.bat
or
...\IA32_Intel64\ifortvars_ia32_intel64.bat


and the line to add is:

For the IA-64 architecture target, the file to edit is

and the line to add is:

IF EXIST "C:\Program Files\VNI\imsl\fnl600\IA64\bin\fnlsetup.bat" @call "C:\Program Files\VNI\imsl\fnl600\IA64\bin\fnlsetup.bat"

It may be necessary to add the paths for the IMSL INCLUDE and library files to Visual Studio.

• Open Microsoft Visual Studio 2003, 2005 or 2008
• Select Tools > Options
• Under Options, select Intel® Fortran > Compilers
• In Visual Studio 2005 or 2008 only, select the Target Platform for which you want to make changes. The default of Win32 is for the IA-32 architecture target.
• Make sure that the desired compiler version is selected.
• At the right of Libraries., click the "..." button.
• Add to the end of the list,
  C:\Program Files\VNI\imsl\fnl600\IA32\lib (for IA-32 architecture target)
  C:\Program Files\VNI\imsl\fnl600\Intel64\lib (for Intel 64 architecture target or)
  C:\Program Files\VNI\imsl\fnl600\IA64\lib (for IA-64 architecture target)
• Click OK.
• At the right of Includes, click the "..." button.
• Add to the end of the list,
  C:\Program Files\VNI\imsl\fnl600\IA32\include\dll (for IA-32 architecture target)
  C:\Program Files\VNI\imsl\fnl600\Intel64\include\dll ( for Intel 64 architecture target or)
  C:\Program Files\VNI\imsl\fnl600\IA64\include\dll for (IA-64 architecture targe)
• Click OK
• Click OK to save the changes.

If you were using the IMSL libraries with Intel Visual Fortran 10.x, you may need to make a change to your source or build options to reflect the change in the default OpenMP* libraries used by the Intel Fortran compiler.

If you followed the recommendation of Visual Numerics* and enabled OpenMP processing for your application, you will probably not have to make changes.

If you were instructed to add to a source file the line:

change this to:

If you added libguide.lib to your build options in other ways, replace it with libiomp5md.lib. You must not specify the /Qopenmp-libs:legacy option as this is incompatible with IMSL.

If you are building a new application, you will need to select one of the sets of IMSL libraries and add the necessary line(s), as described in the compiler documentation, in one of your Fortran source files. Most applications will use these:

Problem: When compiling, you receive an error similar to:

Resolution:
Follow the steps in the sections above for configuring for use from the command line or from Microsoft Visual Studio.

Problem:
When linking, you receive errors similar to:

Resolution:
Add the line:

to one of your Fortran sources. An alternative is to enable OpenMP processing (/Qopenmp), but this may have unwanted side effects if you are not using OpenMP in your application.

If you have comments on this article, specifically, please add them below. If you need assistance using the product, please visit our User Forum or see this support page for further options.

If your application mixes Fortran with C or C++ and the main program is not in Fortran, you must configure Microsoft Visual Studio to search Fortran libraries.  This article describes the process. Visual Studio 2008 is used in the illustrations.  The process is similar for Visual Studio 2005 and Visual Studio.NET 2003, with the exception that Visual Studio .NET 2003 supports development for the "Win32" platform (IA-32 architecture) only.

This article applies to Intel Visual Fortran 10.x and 11.x.

This configuration needs to be done one time only per install of Microsoft Visual Studio.

Open Microsoft Visual Studio.  Select Tools > Options. In the left pane, expand Projects and Solutions and then click on VC++ Directories. (Visual Studio .NET 2003 uses "Projects" instead of "Projects and Solutions")

Click on the New Line button (to the right of the "check mark" button) and enter the following new line if you are using Intel Visual Fortran 11.x:

$(IFORT_COMPILER11)lib\ia32

or the following new line if you are using Intel Visual Fortran 10.x:

$(IFORT_COMPILER10)\ia32\lib

Click OK.

If you are using Visual Studio 2005 or 2008 and will be developing for the Intel 64 or IA-64 architectures, repeat the above steps, using the Platform dropdown to select "x64" (Intel 64) or "Itanium" (IA-64). When entering the path, use "intel64" or "ia64" instead of "ia32".

Additional Notes

If you are using Visual Studio 2005, you must install Visual Studio 2005 Service Pack 1, otherwise your Fortran project will not be found when linking the C/C++ project.

If you need help using Intel Visual Fortran, please visit our User Forum an post a question there.  If you have a comment on this article, you can add one below.