• English

• English

• English

• English

• English
• Japanese

• English

• English
• Japanese

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.

This guide is intended to help Intel® compiler customers build and use the HDF5 library. HDF5 is the latest generation of the HDF libraries, a general purpose library and associated file formats for storing and sharing scientific data. HDF5 is maintained, promoted, and co-developed along with active community support by The HDF Group (THG). THG is a not-for-profit corporation with the mission to sustain HDF technologies and to provide support to HDF user communities. The homepage for THG and HDF5 can be found at http://hdf.ncsa.uiuc.edu/HDF5/.

This application note applies to HDF5, version 1.6.5, as built with the Intel® Fortran Compiler 10.0 and Intel® C++ Compiler 10.0. The procedure outlined in this document are tested with the 10.0 versions of the Intel Fortran Compiler and Intel C++ compiler. Prior versions of the Intel compilers may work as well, but have not been tested. Older verions or newer versions of HDF may work but have not been tested. This document only covers the 10.0 versions of the Intel compilers and HDF5, version 1.6.5.

HDF5 is a data format and an associated software library designed to store, access, manage, exchange, and archive diverse, complex data in continuously evolving heterogeneous computing and storage environments. HDF5 is extensively used with scientific research, engineering development, and other data.

This application note demonstrates the framework for building HDF5 with the Intel compilers but does NOT claim to represent all possible configurations and variations of the build for all possible target environments.

The HDF5 source files should be obtained from HDF5 Software downloads page at http://www.hdfgroup.org/HDF5/release/obtain5.html.

Please note the External Library requirements for SZIP and ZLIB and download those if you do not already have those libraries.

Licensed users of the Intel compilers may download the most recent versions of the compiler from the Intel® Download Center, which is accessed by logging into your account at Intel® Registration Center

Intel® Compilers for Linux*
http://www.intel.com/cd/software/products/asmo-na/eng/compilers/284264.htm

Intel® Compilers for Mac OS*
http://www.intel.com/cd/software/products/asmo-na/eng/270528.htm

Software: As mentioned on the HDF5 software downloads page, either SZIP-2.0 or ZLIB libraries can be used for file compression/decompression. Precompiled binaries or sources are available from the HDF5 Software Downloads page for these two libraries.

SZIP: Determine an appropriate location to install SZIP. /usr/local/szip-2.0 may be a reasonable choice. If you wish to build and install szip from the source files, use the procedure shown below:

export CC=icc
export CXX=icpc
export F77=ifort
export CFLAGS='-O3 -xP -ip'
export CXXFLAGS='-O3 -xP -ip'
export FFLAGS='-O3 -xP -ip'
tar -zxvf szip-2.0.tar.gz
cd szip-2.0
./configure --prefix=/usr/local/szip-2.0
make
make check
make install

The above example uses the BASH shell syntax for setting environment variables. For other shells, use the appropriate commands to set environment variables CC, CXX, etc. before the make command. Confirm that after the 'make check' command, the result of the tests return the result "All test passed."

Check the directory specified by your --prefix= setting. This directory should contain lib/ and include/ directories. For more information on building szip, consult the file named INSTALL in the source directory.

ZLIB: The information shown is for zlib version 1.2.1. zlib is a general purpose data compression library and is a prerequisite for building HDF5. Determine an appropriate location to install SZIP. /usr/local/zlib-1.2.1 may be a reasonable choice. If you wish to build and install szip from the source files, use the procedure shown below:

export CC=icc
export CFLAGS='-O3 -xP -ip'
tar -zxvf zlib-1.2.1.tar.gz
cd zlib-1.2.1
./configure --prefix=/usr/local/zlib-1.2.1
make
make check
make install

The above example uses the BASH shell syntax for setting environment variables. For other shells, use the appropriate commands to set environment variables CC, CXX, etc. before the make command. Confirm that after the 'make check' command, the result of the tests return the result "All test passed".

Check the directory specified by your --prefix= setting. This directory should contain lib/, include/, and share/ directories. For more information on building szip, consult the file named "INSTALL" in the source directory.

HDF5 uses an Autoconf "configure" script to determine the build environment and tools and create the necessary build configuration. The first step is to set environment variables to control which compilers are used for the build. These environment variables select the Intel C++ Compiler and the Intel Fortran Compiler.

export CC=icc
export F9X=ifort
export CXX=icpc

As shown above, the environment CC, CXX and F9X are used to specify which compilers are used to build HDF5. The example shown above uses both the Intel C++ Compiler ( CC=icc CXX=icpc ) and the Intel Fortran Compiler ( F9X=ifort ). Note that the Intel C++ compiler driver is named 'icpc'. Do NOT use 'icc' as the C++ compiler. The Intel compilers are GNU compatible, thus you may mix and match the Intel compilers with GNU compilers for C++ and Fortran. However, the mixing of GNU compilers with Intel compilers has not been tested with this application.

There are environment variables such as CFLAGS to pass compiler options to the C compiler. However, the configuration script will automatically detect the Intel compilers and use the appropriate optimization options. Thus, the user need not specify optimization settings unless one wants to override the default settings set by configure.

tar -zxvf hdf5-1.6.5.tar.gz
cd hdf5-1.6.5
./configure --prefix=/usr/local/hdf5-1.6.5 --enable-fortran --enable-cxx
... output of configure ...
make
... watch for fatal errors ...
make check
... verify that all tests return "PASS"
make install

As shown above, the environment CC, CXX and F9X are used to specify which compilers are used to build HDF5. The example shown above uses both the Intel C++ Compiler ( CC=icc CXX=icpc ) and the Intel Fortran Compiler ( F9X=ifort ). Note that the Intel C++ compiler driver is named 'icpc'. Do NOT use 'icc' as the C++ compiler. The Intel compilers are GNU compatible, thus you may mix and match the Intel compilers with GNU compilers for C++ and Fortran. However, the mixing of GNU compilers with Intel compilers has not been tested with this application.

The configure script has a lot of possible options. To learn all of the possible configuration options, see the help provided in the output of "./configure --help" or read the contents of the file README provided in the OpenMPI tarball.

There is user documentation in the doc/html subdirectory of the source file directory. Look for the file "index.html" and view this file in a browser. This doc/html directory can be copied over to the installation directory.

In general, user program include <hdf5.h> and link with -lhdf5. Additional libraries may be necessary. Please see the user documentation for all the details on the use of HDF5. Users are encouraged to use the compiler helper scripts h5cc, h5fc and h5c++ to build their applications. These helper scripts are installed in the bin/ subdirectory of the installation directory.

This note has shown how to perform a simple build of HDF5* using the Intel compilers. Benefits of using this Intel compiler build of HDF5 include improved optimization and compatibility with the Intel compiler generated binary files and GNU generated binary files.

At this time, there are no known issues with using the Intel compilers to build HDF5. Please see the HDF5 website http://hdf.ncsa.uiuc.edu/HDF5/ for all known issues and limitations.