1. Intel Fortran Manual
2. Intel Fortran Compiler For Windows

Changes in Update 5 (Intel® Fortran Compiler 19.0.5) Note: macOS. 10.15 Catalina and Xcode. 11.0 are not supported in this release. Users will see issues with installation of the Intel Compilers for 2019 Update 5 and prior releases, no Xcode 11 integration, and other possible errors due to incompatibility. Hi i was usinig mac osx 10.10.5 and intel compiler fortran 2015 and everything worked just fine, after updating to mac osx 10.11 when i use ifort in terminal it says ' command not found ' but gfortran 5.1 works fine. The newly released Absoft Pro Fortran v10 for Mac OS/Intel is the first Fortran suite to include both 32-bit and 64-bit compilers plus a complete development environment designed for Fortran programmers. As the latest offering from Absoft Corporation (Rochester Hills, MI). C compiler for mac free download - Intel C Compiler Professional, Pro Fortran Compiler Suite, PayMaker Mac OS X, and many more programs.

Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, 12.x, 11.x, 11.x and 10.1

As for the.f file type, you're confusing two different matters. The file type determines the source form that the compiler expects, NOT the version of the language standard the code is written for. As it happens, all Fortran 77 code is also Fortran 90 code, and you can write Fortran 90/95 code in fixed-form source.

Navigation

Linux and Mac OS X Compilers Installation Help Center: /en-us/articles/intel-compilers-linux-installation-help

This guide presents silent installation instructions for current and previous versions of Intel compilers. Newer compilers are described first, scroll down for version 11.x or older.

Silent Installation Guide for Intel Compilers for Mac OS* X Versions 14.x, 13.x, and 12.x

Here are the steps you need to follow to install the Intel Composer XE for OS X* version 2013 SP1 aka '14.0' in silent mode.
Step 0) Confirm that the userID for the installation has 'sudo' priviledge. If you are unfamiliar with the 'sudo' command please research that command on the internet to become familiar with it's use. Test your sudo priviledge with a simple sudo command such as 'sudo pwd' or 'sudo ls -l'

Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)
2013 SP1 Example:

Disk image mounts under

• /Volumes/m_fcompxe_2013_sp1.u.vvv (for the Fortran Composer XE 2013 SP1)
• /Volumes/m_ccompxe_2013_sp1.u.vvv (for the C++ Composer XE 2013 SP1)

Mount the image

• sudo hdiutil attach m_fcompxe_2013_sp1.u.vvv.dmg
• sudo hdiutil attach m_ccompxe_2013_sp1.u.vvv.dmg

where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2013_sp1.2.142 is Update 2, version 142 for example)
Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already.
Step 3) Using 'Terminal', change directory to the /Packages folder:

2013 SP1 Example:

• cd /Volumes/m_ccompxe_2013_sp1.X.YYY/Packages
• cd /Volumes/m_fcompxe_2013_sp1.X.YYY/Packages

Step 4) Use 'sudo' to run the Intel installer 'i_install': ./i_install with the silent install options.
Usage: ./i_install [OPTIONS]
For Version 2013 SP1: usage: sudo ./i_install [-s or -h] [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -xd 'xcode folder' -l 'log file' -it '[1/2]' -sd '[yes/no]' -eula 'accept'
User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.

Required Options

• -s : to indicate execute in silent mode
• -l : [optional] to provide a install log file (this file will be created '/tmp' folder. Do not use any path information, just some simple name like 'install.log'.
• -f : -licfile Install silently using the license file provided on the command line. Include the full path to the .lic license file on your system. Typically these are stored in directory /Users/Shared/Library/Application Support/Intel/Licenses/<file>.lic
• Port@host Install silently using the server license available at host
• -sn, -sn Install silently using the serial number provided on the command line
• -eula 'accept' to confirm that you have read the End User Licensing Agreement and have accepted the license conditions. By using silent installation you must accept the EULA and by using the silent installation you have agreed to those terms.

More required Options for all compilers Version 11.1 and above

• -id <install_dir> 'install directory', default install folder is /opt/intel
  • Silent install utility installs all the packages bundled in the meta package.
  • To set the top level install folder for these packages one can use this option
• -xd : 'xcode folder' ( provide Xcode IDE folder for compiler to be integrated with) - /Applications/Xcode.app for example or /Developer/XCode

More required Options for all compilers Version 12.0 and above (Composer XE 2011, Composer XE 2013, Composer XE 2013 SP1)
12.0 and 12.1 versions:

• -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
  • User has option to install either command line alone and/or integrate with xcode IDEenviromen
  • Default install type is 3

More required options for all compilers version 13.0, 13.1, and 14.0: Composer XE 2013 and 2013 SP1 versions:

• -it: install type; 1. Command line install 2. both, command line and Xcode environment.
  • User has option to install either command line alone or integrate with Xcode IDE enviroment
  • Default install type is 2
• -sd: indicates agreement to participate in Intel(R) Software Improvement Program, by default is 'no'

Silent Installation Guide for Intel Compilers for Mac OS* X Version 11.x

Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 11.0 and higher in silent mode.

Step 0) Login as an administrative user or root. If you have sudo priviledge, become root user in a Terminal window with:

• sudo bash
• and enter your user password, then enter command
• su -

Step 1) Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. OR If you are working from a terminal window, use the hdiutil command to mount the compiler installer disk image (.dmg)

11.0 Example (11.1 is similar):

Disk image mounts under

• /Volumes/m_cprof_p_11.0.0xx (for the 11.0 Fortran Compiler) or
• /Volumes/m_cproc_p_11.0.0xx (for the 11.0 C++ Compiler)

Mount image with

• hdiutil attach m_cprof_p_11.0.0xx.dmg
• hdiutil attach m_cproc_p_11.0.0xx.dmg

12.0 Example:

Disk image mounts under

• /Volumes/m_fcompxe_2011.u.vvv (for the 12.0 Fortran Compiler) or
• /Volumes/m_ccompxe_2011.u.vvv (for the 12.0 C++ Compiler)

Mount image with

• hdiutil attach m_fcompxe_2011.u.vvv.dmg
• hdiutil attach m_ccompxe_2011.u.vvv.dmg

where 'u' is the update number ( 0, 1, 2, 3, etc) and where 'vvv' is the specific version ( 2011.2.142 is Update 2, version 142 for example).

Step 2) Start a 'Terminal' program from Utilities group (if you have not done so already. Do this as root user or use the command 'sudo bash' to become root user)

Step 3) Using 'Terminal' as root user, change directory to the /Plugins folder:

11.0 (similarly for 11.1):

Change directory to the 'Plugins' folder inside /Volumes/m_cprof_p_11.0.0xx

For example:

• cd /Volumes/m_cproc_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins
• cd /Volumes/m_cprof_p_11.0.0xx/m_cproc_p_11.0.0xx.mpkg/Contents/Plugins

12.0:

• cd /Volumes/m_ccompxe_2011.2.142/m_ccompxe_2011.2.142.mpkg/Contents/Plugins
• cd /Volumes/m_fcompxe_2011.2.142/m_fcompxe_2011.2.142.mpkg/Contents/Plugins

Step 4) Run installer 'i_install': ./i_install with the silent install options.

Usage: ./i_install [OPTION]

For version 11.0: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -eula 'accept'

For version 11.1: usage: ./i_install [-s or -h] -l 'log file' -f 'license file or folder or port@host' -sn 'serialnumber' -xd 'xcode folder' -id 'install folder' -eula 'accept'

For Version 12.0: usage: ./i_install [-s or -h] -l 'log file' [-f 'license file or folder or port@host'] or [-sn 'serialnumber'] -it '[1/2/3]'-xd 'xcode folder' -id 'install folder' -eula 'accept'

User can provide a valid serial number following the -sn option or a license file with the complete path or port@host for server license following the -f option.

Required Options

• -s : to indicate execute in silent mode
• -l : [optional] to provide a install log file (this file will be created '/tmp' folder
• -f : -licfile Install silently using the license file provided on the command line.
• Port@host Install silently using the server license available at host
• -sn, -sn Install silently using the serial number provided on the command line

Additional Options, Version 11.1 and above

• -id <install_dir> 'install directory', default install folder is /opt/intel
  • Silent install utility installs all the packages bundled in the meta package.
  • To set the top level install folder for these packages one can use this option
  • If install_dir is provided then the mounted system has to be writable for silent installs
  • If the mounted volume is not writable, then user gets'Seems mounted volume is read only file system. Use 'hdiutil attach '<disk-image-name>.dmg' -readwrite -shadow' command, to mount the disk image', message and aborts silent install.
• -xd : 'xcode folder' ( provide xcode IDE folder for compiler to be intgegared with)

Additional Options, Version 12.0 and above

• -it: install type; 1. commandline install 2. xcode integration 3. both, command line and xcode environment.
  • User has option to install either command line alone and/or integrate with xcode IDEenviroment
  • Default install type is 3
• -h Display the silent install usage.

Examples:

Log File

Option, '-l mylog_file' creates a install log file 'tmp/mylog_file', if this argument is not given then'/tmp/pset.log' file is created for logs.

Silent Installation Guide for Intel Compilers for Mac OS* X Version 10.1

Here are the steps you need to follow to install the Intel Compilers for Mac OS X* version 10.1 in silent mode.

1. Mount the *.dmg file with required content using 'Finder', for example, by double-clicking on *.dmg. If you are working from a terminal window, this command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx (for the Fortran Compiler) or /Volumes/m_cc_p_10.1.0xx (for the C++ compiler)
   • hdiutil attach m_fc_p_10.1.0xx.dmg
   • hdiutil attach m_cc_p_10.1.0xx.dmg
2. Start a 'Terminal' program from Utilities group (if you have not done so already). Using 'Terminal' do the following:
3. Copy the contents of the mounted image to a local folder, for example:
   • cp -pR /Volumes/m_fc_p_10.1.00x /Users/f_fc_p_10.1.00x (or the similar command for m_cc_p_10.1.0xx)
4. Change directory to the local 'instman' folder inside the folder you copied in (a), for example:
   • cd /Users/f_fc_p_10.1.00x/instman
5. Export DYLD_LIBRARY_PATH=<instman folder>, for example:
   • export DYLD_LIBRARY_PATH=/Users/f_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
6. (optional) Make changes to ‘si_issa.xml' configuration file to change the default settings, see details below.
7. Run: ./si_secore with the silent install options. Usage: /si_secore [OPTION]

The user must provide a valid serial number following the -sn option and a license file with the complete path following the --licfile option. -n, -sn Install silently using the serial number provided on the command line. The other settings will come from 'si_issa.xml' file in the instman folder or from a custom config file, specified as -c 'your config' on the command line.

• -l, -licfile Install silently using the license file provided on the command line. The other settings will come from 'si_issa.xml' file present in the instman folder or from the -c 'your config' file provided on the command line.
• -c Use ISSA and install parameters that are supplied through this configuration file.
• -h Display the silent install usage.

Precedence Order for Parameters

• If both -sn 'SN' and the -c 'CF' options are provided, the serial number provided via command line overrides the serial number specified in the <SerialNumber> value in the configuration file.
• If both -licfile 'LF' and the -c 'CF' options are provided, the license file provided via command line overrides the license file specified in the <LicenseFile> value in the configuration file.
• If both <SerialNumber> and <LicenseFile> values are provided in the configuration file or as command-line options, silent install will first copy the license file, validate and proceed with the install; if install fails, it will follow the serial number option path.

Configuration File

The default configuration file 'si_issa.xml' is available in the ‘instman' folder. You can use the script file 'pre_sinstall.sh' available in the 'instman' folder to generate an silent install config file. Here is an example of the format of this configuration file

Note: the pkg_id attribute under <Package pkg_id='1'> will set the order in which the tools will be installed. You can change the install order based on dependencies between installed packages. Include the <Proxy> section only if a web proxy server is required to reach the Intel® Software Development Products Registration Center web server.

Examples:

Log File
To create a log file, create a directory named 'WorkArea' within the 'instman' folder. Rerun the installation, and files will be created in the 'WorkArea' folder. The most important file will be secore.log, which is a transcript of the ISSA session.
Silent Install Using ‘sudo'
Users utilizing the ‘sudo' command to perform a silent install need to modify the above procedure. By default, sudo will not preserve the user's DYLD_LIBRARY_PATH setting. The following silent install procedure should be used by sudo users:
To install the compiler with sudo in the 'silent' mode with an interactive shell

1. Mount the product dmg file with required content using Finder, for example, by double-clicking on the dmg file.
2. Start a Terminal program from the Utilities group. Using Terminal, copy the contents of the mounted image to a local folder, for example
   • cp -pR /Volumes/m_fc_p_10.1.00x /Users/m_fc_p_10.1.0xx
3. Change directory to the local instman folder inside the folder you copied in (a), for example:
   • cd /Users/m_fc_p_10.1.00x/instman
4. Start a shell session under bash, for example:
   • sudo /bin/bash
5. Export DYLD_LIBRARY_PATH=<instman folder>, for example:
   • export DYLD_LIBRARY_PATH=/Users/m_fc_p_10.1.00x/instman:$DYLD_LIBRARY_PATH
6. (optional) Make changes to si_issa.xml configuration file to change the default settings, see details below.
7. Run ./si_sicore with options as described above.

To install the compiler with sudo in the 'silent' mode with minimal interaction
The following method uses sudo in a mode suitable for scripted automation.

1. Start a Terminal program from the Utilities, or create a user shell (rsh, X11, etc)
2. Change directories to a working area where the user has write permission. For example, cd /Users/<my user> ,where this is the home directory of user <my user>. This example assumes the user has downloaded or copied the compiler disk image (.dmg) file to this user home directory /Users/<my user>/m_fc_p_10.1.0xx.dmg where '0xx' is the compiler minor version.
3. Mount the compiler disk image. Assumes compiler .dmg file is in your current directory. This command will mount the compiler installer disk image under /Volumes/m_fc_p_10.1.0xx: sudo hdiutil attach m_fc_p_10.1.0xx.dmg
4. Copy the contents of the mounted image to a local folder where you have write permission. For example, if your current directory is user writeable: cp -pR /Volumes/m_fc_p_10.1.0xx /Users/<my user> , where '<my user>' is replaced by your login or user name.
5. Change directories to /Users/<my users>/m_fc_p_10.1.0xx/instman created by the previous copy command: cd /Users/<my user>/m_fc_p_10.1.0xx/instman
6. Use sudo to run the installer, using one of two possible methods, where '<options>' are replaced by si_secore options described above.
   • sudo env DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ./si_secore <options>
   • sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore <options> '
   • For example, to use the serial number XXXX-XXXXXX to install:
     • sudo -c 'DYLD_LIBRARY_PATH=/Users/<my user>/m_fc_p_10.1.0xx/instman ; ./si_secore -n XXXX-XXXXXX '
7. (optional) Remove the compiler installation files. For example,
   • cd /Users/<my user>
   • rm -Rf m_fc_p_10.1.0xx
8. (optional) Unmount the compiler installation image. For example, sudo hdiutil unmount /Volumes/m_fc_p_10.1.0xx
9. Finally, to truly make this sequence suitable for scripting, you can pass your password to the sudo commands above using the -S option to sudo. For example, echo ‘MyPassword' | sudo -S <options> <command> , where ‘MyPassword' is your user password used to run sudo command.

Note

As noted in the Intel® Software Development Product End User License Agreement, the Intel® Software Development Product you install will send Intel the product’s serial number and other system information to help Intel improve the product and validate license compliance. No personal information will be transmitted.

This document provides a summary of new and changed product features and includes notes about features and problems not described in the product documentation.

Please see the licenses included in the distribution as well as the Disclaimer and Legal Information section of these release notes for details. Please see the following links for information on this release of the Intel® Fortran Compiler 18.0.

Change History

This section highlights important changes from the previous product version and changes in product updates.

Changes in Update 5 (Intel® Fortran Compiler 18.0.6)

• Intel® Parallel Studio XE 2018 Update 5 Composer Edition has been updated to include more recent versions of 3rd party components, which include functional and security updates. Users should update to the latest version.
  NOTE: Although the Intel® Parallel Studio XE 2018 installer package for this update release is Update 5, the actual compiler package within this Intel® Parallel Studio XE 2018 Update 5 installation package is the Intel® Compilers 2018 Update 6 component and NOT an Update 5 component. So you will see the Intel® Compilers 2018 Update 6 and not Update 5 in this installer package. The compiler(s) will also identify as 2018 Update 6. Be assured that the 2018.6.xxx directories and product versions 18.0.6 in packages you see during installation from the Intel® Parallel Studio XE 2018 Update 5 release are correct and are for the Intel® Compilers 2018 Update 6 component. We apologize for the confusion in the update numbering between the enclosing Intel® Parallel Studio XE 2018 Update 5 package and the actual Intel® Compilers 2018 Update 6 which is installed and is to be used for this update.

Intel Fortran Manual

Changes in Update 4 (Intel® Fortran Compiler 18.0.4)

• Corrections to reported problems

Changes in Update 3 (Intel® Fortran Compiler 18.0.3)

• -[a]xIcelake-server and -[a]xIcelake-client options added to support Ice Lake microarchitecture
• -[a]xCannonlake option added to support Cannon Lake microarchitecture
• Xcode* 9.3 support
• Corrections to reported problems

Changes in Update 2 (Intel® Fortran Compiler 18.0.2)

• Xcode* 9.2 support
• Corrections to reported problems

Changes in Update 1 (Intel® Fortran Compiler 18.0.1)

• Xcode* 9.1 and macOS* 10.13 support
• Corrections to reported problems

Changes since Intel® Fortran Compiler 17.0 (New in Intel® Fortran Compiler 18.0.0)

• Corrections to reported problems

System Requirements

• A 64-bit Intel®-based Apple* Mac* system host (development for 32-bit is still supported)
• 2GB RAM minimum, 4GB RAM recommended
• 4GB free disk space for all features
• One of the following combinations of macOS*, Xcode* and the Xcode SDK:
  • macOS* 10.13
  • Xcode* 9.4
• If doing command line development, the Command Line Tools component of Xcode* is required

Note: Advanced optimization options or very large programs may require additional resources such as memory or disk space.

How to install the Intel® Fortran Compiler

If you received the compiler product on DVD insert the DVD. Locate the disk image file (xxx.dmg) on the DVD and double-click. If you received the compiler product as a download, double-click the downloaded file. When the disk image opens, double-click on the xxx.app file to begin installation. Follow the prompts to complete installation.

How to use the Intel® Fortran Compiler

Intel® Parallel Studio XE 2018: Getting Started with the Intel® Fortran Compiler 18.0 for macOS* at <install-dir>/documentation_2018/en/compiler_f/ps2018/get_started_mf.htm contains information on how to use the Intel® Fortran Compiler from the command line and from Xcode*.

Documentation

Product documentation is linked from <install-dir>/documentation_2018/en/compiler_f/ps2018/get_started_mf.htm.

Offline Core Documentation Removed from the Installed Image

Offline core documentation is removed from the Intel® Parallel Studio XE installed image. The core documentation for the components of Intel® Parallel Studio XE are available at the Intel® Software Documentation Library for viewing online. You can also download an offline version of the documentation from the Intel® Software Development Products Registration Center: Product List > Intel® Parallel Studio XE Documentation.

User and Reference Guides, What's New and Release Notes, Installation Guides

Refer to the Intel® Parallel Studio XE Support – Documentation for additional User and Reference Guides, What’s New and Release Notes, and Installation Guides.

Intel-provided Debug Solutions

Intel®-provided debug solutions are based GNU* GDB. Please see Intel® Parallel Studio 2018 Composer Edition Fortran - Debug Solutions Release Notes for further information.

Samples

Product samples are now available online at Intel® Software Product Samples and Tutorials

Redistributable Libraries

Refer to the Redistributable Libraries for Intel® Parallel Studio XE for more information.

Technical Support

If you did not register your compiler during installation, please do so at the Intel® Software Development Products Registration Center. Registration entitles you to free technical support, product updates and upgrades for the duration of the support term.

For information about how to find Technical Support, Product Updates, User Forums, FAQs, tips and tricks, and other support information, please visit: http://www.intel.com/software/products/support/

Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.

Compatibility

In general, object code and modules compiled with earlier versions of Intel Fortran Compiler for Linux* (8.0 and later) may be used in a build with version 17. Exceptions include:

• Sources that use the CLASS keyword to declare polymorphic variables and which were built with a compiler version earlier than 12.0 must be recompiled.
• Objects built with the multi-file interprocedural optimization (-ipo) option must be recompiled with the current version.
• Objects that use the REAL(16), REAL*16, COMPLEX(16) or COMPLEX*32 datatypes and which were compiled with versions earlier than 12.0 must be recompiled.
• Objects built for the Intel® 64 architecture with a compiler version earlier than 10.0 and that have module variables must be recompiled. If non-Fortran sources reference these variables, the external names may need to be changed to remove an incorrect leading underscore.
• Modules that specified an ATTRIBUTES ALIGN directive outside of a derived type and were compiled with versions earlier than 11.0 must be recompiled. The compiler will notify you if this issue is encountered.
• Modules that specified an ATTRIBUTES ALIGN directive inside a derived type declaration cannot be used by compilers older than 13.0.1.
• The implementation of the Fortran 2008 submodules feature required extensive changes to the internal format of binary .mod files. Therefore module files created by the version 16.0 or newer Fortran compiler cannot be used with version 15.0 or older Fortran compilers.

Stack Alignment Change for REAL(16) and COMPLEX(16) Datatypes

In versions prior to 12.0, when a REAL(16) or COMPLEX(16) (REAL*16 or COMPLEX*32) item was passed by value, the stack address was aligned at 4 bytes. For improved performance, the version 12 and later compilers align such items at 16 bytes and expects received arguments to be aligned on 16-byte boundaries. This change is also compatible with gcc.

This change primarily affects compiler-generated calls to library routines that do computations on REAL(16) values, including intrinsics. If you have code compiled with earlier versions and link it with the version 12 libraries, or have an application linked to the shared version of the Intel run-time libraries, it may give incorrect results.

In order to avoid errors, you must recompile all Fortran sources that use the REAL(16) and COMPLEX(16) datatypes if they were compiled by compiler versions earlier than 12.0.

New and Changed Features

The Intel® Fortran Compiler now supports all features from the Fortran 2008 standard. Additional Fortran 2008 features added in the Intel® Fortran 18.0 release are noted below. Please refer to the Fortran 2008 Standard (PDF) and the proposed draft Fortran 2015 Standard (PDF) if necessary.

Features from Fortran 2008

• COMPILER_OPTIONS and COMPILER_VERSION in ISO_FORTRAN_ENV
• COMPLEX arguments to trigonometric and hyperbolic intrinsic functions
• FINDLOC intrinsic function
• Optional argument BACK in MAXLOC and MINLOC intrinsic functions
• Multiple type-bound procedures in a PROCEDURE list
• Passing a non-pointer data item to a pointer dummy argument
• Polymorphic assignment with allocatable Left Hand Side (LHS)
• Allocatable components of recursive type and forward reference
• Data statement restrictions removed

Features from OpenMP*

Language features for task reductions from the OpenMP* Technical Report 4 : Version 5.0 Preview 1 specifications are now supported.

TASKGROUP now has the TASK_REDUCTION clause.
TASK includes now has the IN_REDUCTION clause.
TASKLOOP now has the REDUCTION and IN_REDUCTION clauses.

New monotonic, overlap and lastprivate keywords for OpenMP* SIMD directive:

!$omp ordered simd overlap(overlap_index)
!$omp ordered simd monotonic([var:step]s)
!$omp simd lastprivate(conditional:[vars])

For more information, see the compiler documentation or the link to the OpenMP* Specification above.

New and Changed Directives

New and Changed Compiler Options

Please refer to the compiler documentation for details

• -qopenmp replaces -openmp
• -assume contiguous_pointer and -assume contiguous_assumed_shape options
• -check contiguous

For a list of deprecated compiler options, see the Compiler Options section of the documentation.

New -qopenmp Compiler Option replaces -openmp

To enable the OpenMP* feature, use -qopenmp. The compiler no longer accepts the previous spelling -openmp

Enhanced -init=[keyword] Compiler option

The option already allows scalars and arrays to be initialized with ZERO or SNAN. Feature support extends this to HUGE and MINUS_HUGE {+/- largest representable integer or real}, TINY and MINUS_Tiny {+/- smallest representable integer or real}, and INFINITY and MINUS_INFINITY for +/- IEEE Infinity.

All –o* options replaced by –qo* options

All the –o* options deprecated in the previous release have been replaced with –qo* options in this release with one noted exception, there is no change to the –o option for Linux* and macOS* used to name the output file.

A new diagnostic is issued when any now replaced –o option is used. For example:

$ ifort -openmp example.f90
ifort: command line error: option '-openmp' is not supported. Please use the replacement option '-qopenmp'

Options affected:

-offload-attribute-target=<target>
-offload-option,<target>,<tool>,<opts>
-[no-]offload[=<arg>]
-[no-]openmp
-openmp-lib=<arg>
-openmp-link=<arg>
-[no-]openmp-offload
-[no-]openmp-simd
-openmp-stubs
-openmp-threadprivate=<arg>
-openmp-report[=<level>]
-openmp-task=<arg>
-opt-args-in-regs=<arg>
-[no-]opt-assume-safe-padding
-opt-block-factor=<arg>
-[no-]opt-calloc
-[no-]opt-class-analysis
-[no-]opt-dynamic-align
-[no-]opt-gather-scatter-unroll
-[no-]opt-jump-tables=<arg>
-opt-malloc-options=<arg>
-[no-]opt-matmul
-[no-]opt-mem-layout-trans=<arg>
-[no-]opt-multi-version-aggressive
-[no-]opt-prefetch[=<val>]
-opt-prefetch-distance=<arg>
-opt-ra-region-strategy[=<arg>]
-[no-]opt-report-embed
-opt-report-file=<arg>
-opt-report-filter=<arg>
-opt-report-format=<arg>
-opt-report-phase=<arg>
-opt-report-routine=<arg>
-opt-report-help
-opt-report[=<arg>]
-opt-report-per-object
-opt-streaming-cache-evict=<arg>
-opt-streaming-stores=<arg>
-[no-]opt-subscript-in-range
-opt-threads-per-core=<arg>

New -assume contiguous_pointer and -assume contiguous_assumed_shape Compiler options

These are new options to assert that all assumed shape arrays and/or pointers have unit stride.

New -check contiguous Compiler option

The -check contiguous compiler option help to diagnose non-contiguous pointer assignment to CONTIGUOUS pointer. The -check all option includes this check.

New option -fimf-use-svml to force the usage of SVML

New option forces use of SVML where currently LIBM is used, for scalar math. This guarantees bitwise-same result of computations made with vectorized code vs computations made with scalar code. With this feature the compiler vectorizes math functions in -fp-model precise FP model and vectorized code produces results consistent with scalar code results.

Compile time dispatching for SVML calls

The compiler default behaviour is changed for SVML functions and a call to cpu-specific SVML entry is performed. Specifying new option -fimf-force-dynamic-target reverts to the previous behavior and dynamic SVML dispatching is used.

New -qopt-zmm-usage option

You can tune the zmm code generation done by the compiler with the new additional option -qopt-zmm-usage:low|high. The argument value of low provides a smooth transition experience from Intel® Advanced Vector Extensions 2 (Intel® AVX2) ISA to Intel® Advanced Vector Extensions 512 (Intel® AVX-512) ISA on a Skylake server microarchitecture target, such as for enterprise applications. Tuning for ZMM instruction use via explicit vector syntax such as #pragma omp simd simdlen() is recommended. The argument value of high is recommended for applications, such as HPC codes, that are bounded by vector computation to achieve more compute per instruction through use of the wider vector operations. The default value is low for Skylake server microarchitecture-family compilation targets and high for combined compilation targets.

Support Removed

Support for installation on OS X 10.11 or earlier has been removed

Support has been removed for installation and use on these operating system versions. Intel recommends migrating to a newer version of these operating systems.

Support for Xcode* 7.x or earlier has been removed

Support has been removed for these Xcode versions. Intel recommends migrating to a newer version of these developer toolsets.

Known Limitations

Xcode* requires explicit acceptance of Intel bundle at startup for integration to be installed

Beginning with Xcode* 6.3.2, the IDE integration for Intel® Parallel Studio XE does not complete installation until the next time Xcode is started after completing the product installation. When Xcode* is started, you will see a dialog:

Intel Fortran Compiler For Windows

The dialog is titled “Unexpected code bundles”, and mentions that Xcode found one or more code bundles not provided by Apple. It then has two buttons, one to “Load Bundles” and one to “Skip Bundles”. “Load Bundles” is required to be clicked to complete the Intel Parallel Studio XE IDE integration. Clicking “Skip Bundles” will cause the Intel tools to not be selectable in Xcode*.

Certain uses of OMP THREADPRIVATE with COMMON block name not diagnosed per OpenMP 4.5 rules

The OpenMP* 4.5 rules states that if a threadprivate directive specifying a common block name appears in one program unit, then such a directive must also appear in every other program unit that contains a COMMON statement specifying the same name. It must appear after the last such COMMON statement in the program unit. The Intel Fortran compiler does not properly diagnose this.

For example, the following program does not conform to the OpenMP* 4.5 specification and ifort does not diagnose and issue an error for the COMMON statements following the OMP THREADPRIVATE statement according to the rule above.

PROGRAM ex1
COMMON /common_blk1/x
!$OMP THREADPRIVATE(/common_blk1/)

COMMON /common_blk1/y
COMMON /common_blk1/z

END PROGRAM

Fortran 2008 and Fortran 2015 Feature Summary

The Intel® Fortran Compiler now supports all features from the Fortran 2008 standard. The Intel® Fortran Compiler also supports features from the proposed draft Fortran 2015 standard. Additional features will be supported in future releases. Features from the proposed Fortran 2015 standard supported by the current version include:

• Support for all features from “Technical Specification 29113 Further Interoperability with C”, planned for inclusion in Fortran 2015. These include:
  • Assumed type (TYPE(*))
  • Assumed rank (DIMENSION(..))
  • relaxed restrictions on interoperable dummy arguments
  • ISO_Fortran_binding.H C include file for use by C code manipulating “C descriptors” used by Fortran

Disclaimer and Legal Information

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL(R) PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.

Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked 'reserved' or 'undefined.' Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.

Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm

Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. Go to:

The Intel® Fortran Compiler is provided under Intel’s End User License Agreement (EULA).

Please consult the licenses included in the distribution for details.

Intel, Intel logo, and Cilk are trademarks of Intel Corporation in the U.S. and other countries.

* Other names and brands may be claimed as the property of others.

Copyright © 2019 Intel Corporation. All Rights Reserved.

For more complete information about compiler optimizations, see our Optimization Notice.