Intel Fortran Compiler Standard Edition For Mac

The Standard Edition of this product consists of the Intel® Visual Fortran Compiler, the Intel® Debugger, the Intel® Array Visualizer, integration into Microsoft. Visual C.NET. 2002 or 2003, and code coverage and test prioritization tools.

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 19.1.

Change History

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

Changes in Update 1 (Intel® Fortran Compiler 19.1.1)

• Corrections to reported problems.
• Support for integration with Xcode 11 is removed.

Changes since Intel® Fortran Compiler 19.0 (New in Intel® Fortran Compiler 19.1.0)

• New compiler options:
• Corrections to reported problems

System Requirements

• A 64-bit Intel®-based Apple* Mac* system
• 2GB RAM minimum, 4GB RAM recommended
• 14GB free disk space for all features
• One of the following combinations of macOS*, Xcode* and the Xcode SDK:
  • macOS* 10.15 and Xcode 11.x -- Note: Fortran Integrations into Xcode is removed. However, Xcode Command Line Tools are needed for command line to function. SEE HERE
  • macOS 10.14 and Xcode 10.x
• If doing command line development, the Command Line Tools component of Xcode* is required
• Build Rules Missing: See Known Issues or GO HERE

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

Installation instructions are shipped with all Intel® Software Development Products as part of the documentation.

Note that user should have an administrative authorities to install Intel® Fortran Compiler on macOS*.

Jtds sql server drivers for mac. Please refer to Installation FAQ for more details on installation questions.

How to use the Intel® Fortran Compiler

Intel® Parallel Studio XE 2020: Getting Started with the Intel® Fortran Compiler 19.1 for macOS* at <install-dir>/documentation_2020/en/compiler_f/ps2020/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

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. Offline documentation for older versions is also available from the Intel® Software Development Products Registration Center: Product List > Intel® Parallel Studio XE Documentation and fromDownload 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 2020 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 19.1. 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.
• Objects built with Intel Fortran Compiler version 18.0 and earlier version of regcall calling convention must be recompiled with 19.0 or newer. Intel library libirng uses regcall. Version of this library shipped with 19.0 compiler version or newer is not compatible with older versions. regcall is implicitly used by following attribute:
  !DIR$ ATTRIBUTES [att,] VECTOR [:clause] [, att].. :: routine-name

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 Compiler Features

New features from Fortran 2018

• Enhancements to the IMPLICIT statement allow specifying that all external procedures must declared EXTERNAL
• Enhancements to the GENERIC statement permit it to be used to declare generic interfaces
• The locality of variables may now be specified on a DO CONCURRENT statement
• Enhancements to edit descriptor forms E, D, EN, ES, and G allow a field width of zero, analogous to the F edit descriptor
• The exponent width e in a data edit descriptor may now be zero, analogous to a field width of zero
• The RN edit descriptor now rounds to nearest as specified by Fortran 2018 and ISO/IEC/IEEE 60559:2011
• The EX edit descriptor allows for hexadecimal format output of floating point values. Hexadecimal format floating point values are allowed on input.
• SIZE= may be specified for non-advancing I/O
• The values for SIZE= and POS= in an INQUIRE statement for pending asynchronous operations have been standardized
• The value assigned to the RECL= specifier in an INQUIRE statement now has standardized values
• A new form of the intrinsic function CMPLX does not require the KIND= keyword if the first argument is type COMPLEX
• The arguments to the SIGN function may be of different kinds
• INTEGER and LOGICAL arguments to intrinsic procedures are no longer required to be of default kind
• The named constants STAT_FAILED_IMAGE and STAT_UNLOCKED_FAILED_IMAGE have been defined in the intrinsic
  ISO_FORTRAN_ENV module
• The non-block DO statement and the arithmetic IF statement are now deleted in Fortran 2018. Intel® Fortran fully supports features deleted in the FORTRAN standard
• COMMON, EQUIVALENCE and BLOCKDATA statements are now obsolescent
• The labeled form of DO loops is now obsolescent
• Locality of variables in DO CONCURRENT constructs can now be declared on the DO CONCURRENT statement
• Specific names of intrinsic procedures are now obsolescent
• FAIL IMAGE statement allows debugging recovery code for failed images without having to wait for an actual image failure
• The named constants STAT_FAILED_IMAGE and STAT_UNLOCKED_FAILED_IMAGE have been defined in the intrinsic
  ISO_FORTRAN_ENV module
• An optional argument STAT= has been added to ATOMIC_REF and ATOMIC_DEFINE intrinsic procedures
• Optional STAT= and ERRMSG= specifiers have been added to the MOVE_ALLOC intrinsic procedure, to image selectors, and to the CRITICAL statement and construct
• Atomic subroutines ATOMIC_ADD, ATOMIC_AND, ATOMIC_CAS, ATOMIC_FETCH_ADD, ATOMIC_FETCH_AND, ATOMIC_FETCH_OR, ATOMIC_FETCH_XOR, ATOMIC_OR, and ATOMIC_XOR have been implemented
• Collective subroutines CO_BROADCAST, CO_MAX, CO_MIN, CO_REDUCE, and CO_SUM have been implemented
• The SELECT RANK construct has been implemented allowing manipulation of assumed rank dummy arguments
• The compiler will now diagnose the use of nonstandard intrinsic procedures and modules as required by Fortran 2018
• Transformational intrinsic functions from the intrinsic modules ISO_C_BINDING, IEEE_ARITHMETIC, and IEEE_EXCEPTIONS are now allowed in specification expressions
• You can now specify the optional argument RADIX for the IEEE_GET_ROUNDING_MODE and IEEE_SET_ROUNDING_MODE intrinsic module procedures
• The optional ROUND argument has been added to the IEEE_RINT function in the intrinsic module IEEE_ARITHMETIC
• The intrinsic module IEEE_ARITHMETIC now includes the functions IEEE_FMA, IEEE_SIGN_BIT, IEEE_NEXT_UP and IEEE_NEXT_DOWN
• The intrinsic module procedures IEEE_MAX, IEEE_MIN, IEEE_MAX_MAG, and IEEE_MIN_MAG have been implemented
• The intrinsic module procedures IEEE_INT and IEEE_REAL have been implemented
• The intrinsic module IEEE_EXCEPTIONS now contains a new derived type, IEEE_MODES_TYPE, which can be used to save and restore the IEEE_MODES using the IEEE_GET_MODES and the IEEE_SET_MODES intrinsic module procedures
• A new rounding mode, IEEE_AWAY has been added
• SUBNORMAL is now synonymous with DENORMAL
• IEEE_QUIET_EQ, IEEE_QUIET_NE, IEEE_QUIET_LT, IEEE_QUIET_LE, IEEE_QUIET_GT, IEEE_QUIET_GE, IEEE_SIGNALING_EQ, IEEE_SIGNALING_NE, IEEE_SIGNALING_GT, IEEE_SIGNALING_GE, IEEE_SIGNALING_LT, and IEEE_SIGNALING_LE intrinsic module procedures have been implemented

New features from OpenMP 5.0*

• IF clause on SIMD directive
• NONTEMPORAL clause on SIMD directive
• Inclusive/exclusive scan operations in SIMD and TARGET SIMD constructs.

Changed compiler behavior

• Previous compiler versions erroneously permitted a PRIVATE or SEQUENCE statement to appear prior to the declaration of any type parameters in a derived type declaration. Intel® Fortran Compiler 19.1 no longer permits this behavior.
• The INQUIRE statement now uses realpath’/’GetFullPathNameA’ and uses the resulting canonicallized file-paths if the calls succeeds. An example of the change is:
  Open file as “bar/foo”.
  Before:
  Inquire whether “./bar/foo”, “bar//foo” or “bar/./bar/foo” is open – it is not.
  After:
  Inquire whether “./bar/foo”, “bar//foo” or “bar/./bar/foo” is open – it is.
• In 19.0 compiler version, all procedures with the exception of C_F_POINTER from the intrinsic module ISO_C_BINDING were made PURE per the Fortran 2018 standard. Interpretation 18/007 declared that making C_F_PROCPOINTER PURE was a mistake. 19.1 complies with this interpretation and makes C_F_PROCPOINTER IMPURE.

New and Changed Compiler Options

Please refer to the compiler documentation for details. Following new compiler options added:

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

-assume [no]old_inquire_recl

Determines the value of the RECL= specifier on an INQUIRE statement for an unconnected unit or a unit connected for stream access.

-assume [no]old_ldout_zero

Determines the format of a floating-point zero produced by list-directed output. old_ldout_zero uses exponential format, no_old_ldout_zero uses fractional format.

-check [no]udio_iostat

Determines whether standard conformance checking occurs when user defined derived type input/output procedures are executed.

Support Deprecated

Nothing to report

Support Removed

Loop Profiler

The Loop Profiler feature is removed in Intel® Fortran Compiler 19.1. The following compiler options related to Loop Profiler are removed: -profile-loops=keyword, -profile-loops-report=value -profile-functions, -guide-profile.

32-bit applications are no longer supported

Starting with the 19.0 release of the Intel® Fortran Compiler, macOS 32-bit applications are no longer supported.
If you want to compile 32-bit applications, you should use an earlier version of the compiler and Xcode* 9.4 or earlier.

Fortran Integration into Xcode removed

Xcode integration capabilities within our Fortran Compiler bundle have been removed. Command line interface remains fully functional for macOS.

Keep in mind that installation of Xcode is still recommended, as command line tools from Xcode are required by the command line compiler. However, you can install just the Xcode Command Line Tools with this command from a terminal window:

Known Limitations

Slow License Checkout macOS 10.15

The license checkout performance on macOS Catalina 10.15 is roughly 1.1 seconds per source file. This is a 10x slowdown on this OS compared to previous versions of macOS. We are evaluating our license technology for a solution but at this time we have not root caused the issue. If this slowdown is an issue, please revert back to the previous macOS 10.14 where this slowdown does not occur.

Error 'no rule to process file' within Xcode* 10 and 11

macOS*’s XCode 10 and 11 come with a new build system and it is configured as the default. Currently, the Intel Fortran Compiler does not support it. You will see the error 'no rule to process file' when building an Intel Fortran Compiler project within XCode. Please switch to “Legacy Build System” in Project Settings to build your Fortran project in Xcode.

For more details please find this article.

Keep in mind, support for Xcode Integration is deprecated and will be removed in a future update - SEE THIS NOTE

Fortran 2008 and Fortran 2018 Feature Summary

The Intel® Fortran Compiler supports full Fortran 2008 standard and most features from the Fortran 2018 standard. New Fortran 2018 features supported by the current version are listed in the 'New features from Fortran 2018' section.

Please refer to the Fortran 2008 Standard (PDF) and the Fortran 2018 Standard (PDF) if necessary.

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, the Intel logo, the Intel Inside logo, Xeon are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.

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

© Intel Corporation. All Rights Reserved.

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

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 19.0.

Change History

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

Changes in Update 8 (Intel® Fortran Compiler 19.0.8)

This is release for Intel® Compilers 2019 Update 8, compilers version 19.0.8. Highlights for this release:

• Intel(R) Parallel Studio XE 2019 Update 6 Composer Edition contains Compiler Update 8.
• Compilers Update 6 and 7 are not available to the general public.
• Compilers Update 6 and 7 were special releases not available to all customers.
• Corrections to reported problems.
• Includes certain functional and security updates. We recommend updating for these functional and security updates.
• Floating License Server Upgrade required if you upgrade from from 2019 Update 3 or older

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. Users are advised to delay upgrading to macOS* 10.15 and Xcode 11 until we officially support this environment. Support for macOS* 10.15 and Xcode 11 will be provided in a future release.
• Support for Xcode 10.3
• Floating License Server Upgrade required if you upgrade from from 2019 Update 3 or older
• Corrections to reported problems

Changes in Update 4 (Intel® Fortran Compiler 19.0.4)

• Corrections to reported problems

Changes in Update 3 (Intel® Fortran Compiler 19.0.3)

• Xcode* 10.1 support
• Previous compiler versions erroneously permitted a PRIVATE or SEQUENCE statement to appear prior to the declaration of any type parameters in a derive type declaration. Intel® Fortran Compiler 19.0.3 no longer permits this behavior.
• Corrections to reported problems

Changes in Update 2 (Intel® Fortran Compiler 19.0.2)

• Intel® Fortran Compiler 19.0 Update 2 includes functional and security updates. Users should update to the latest version.

Changes in Update 1 (Intel® Fortran Compiler 19.0.1)

• macOS* 10.14 and Xcode* 10 support
• New code names supported by -[a]x, -mtune and -march options
• code names supported : cascadelake, kabylake, coffeelake, amberlake, whiskeylake
• Corrections to reported problems

Changes since Intel® Visual Fortran Compiler 18.0 (New in Intel® Fortran Compiler 19.0.0)

• New -[a]xcannonlake and -mtune=cannonlake options
• -m<feature> support
• -rcd option deprecated
• Corrections to reported problems

System Requirements

• A 64-bit Intel®-based Apple* Mac* system
• 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, 10.14
  • Xcode* 9.4, 10.0
• 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

Installation instructions are shipped with all Intel® Software Development Products as part of the documentation.

Note that user should have an administrative authorities to install Intel® Fortran Compiler on macOS*.

Please refer to Installation FAQ for more details on installation questions.

How to use the Intel® Fortran Compiler

Intel® Parallel Studio XE 2019: Getting Started with the Intel® Fortran Compiler 19.0 for macOS* at <install-dir>/documentation_2019/en/compiler_f/ps2019/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_2019/en/compiler_f/ps2019/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. Offline documentation for older versions is also available 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 2019 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 19.0. 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 supports all features from the Fortran 2008 standard.

Please refer to the Fortran 2008 Standard (PDF) and the Fortran 2018 Standard (PDF) if necessary.

Intel® Parallel Studio XE 2019 Update 4 and newer updates require version 2.9 or higher of the Intel Software License Manager for floating licenses

The Intel® Software License Manager has been updated to version 2.9 for this release. You must upgrade to this version before installing Intel Parallel Studio XE 2019 Update 4 and newer updates with a floating license. Please refer for more details:

Intel® Software License Manager Download
Intel® Software License Manager Release Notes

Features from Fortran 2018

• Coarray events
• Intrinsic function coshape
• Default accessibility for entities accessed from a module
• Import Enhancements
• All standard proceduress in ISO_C_BINDING other than C_F_POINTER are now PURE

Features from OpenMP*

• User-Defined Reductions from the OpenMP* 4.5 specifications are now supported:
  !$omp declare reduction(reduction-identifier: type-list : combiner) [initializer-clause]
• The F2008 standard added the BLOCK/ENDBLOCK construct. It is now allowed to use this construct inside an OMP region.
• ASSERT clause for !$OMP SIMD directive
  Directs the compiler to assert when the vectorization fails. Similar to deprecated !DIR$ SIMD ASSERT.

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

New and Changed Directives

• New clause for dynamic alignment in the VECTOR directive:
  !DIR$ VECTOR DYNAMIC_ALIGN[(POINTER)]
  !DIR$ VECTOR NODYNAMIC_ALIGN
  The compiler generates a peel loop for the specified pointer. If no pointer is specified, the compiler automatically decides for which pointer to generate aligned loads and stores, or else doesn’t generate a peel loop. With the nodynamic_align clause, the compiler will not generate a peel loop.
• New clause for vector length in VECTOR directive:
  !DIR$ VECTOR VECTORLENGTH(vl1, vl2, .., vln)
  Vectorizer chooses best vector length from the list according to cost model. If all vector lengths from the list are not profitable, the loop remains scalar.

New and Changed Compiler Options

Please refer to the compiler documentation for details

• -m<feature> support
• New -[a]xcannonlake and -mtune=cannonlake options

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

-qopenmp-simd is on by default

-qopenmp-simd option enables OpenMP* SIMD compilation. It is set by default now. In order to disable it please use -qno-openmp-simd- option explicitly.

New -check:shape and -warn:shape options

These switches tell the compiler to produce errors or warnings when shapes of arrays do not match on assignments. This check is done for assignments only (and implicit assignments resulting from an allocate with source= syntax).

Value safe simd options for !$OMP SIMD directive

!$OMP SIMD directive overrides FP value and exception safe settings. Following options introduced in 19.0 Update 1 change that legacy behavior and produce value and exception safe code even for SIMD loops:

• -q[no-]simd-honor-fp-model: Tells the compiler to obey the selected floating-point model when vectorizing SIMD loops
• -q[no-]simd-serialize-fp-reduction: Tells the compiler to serialize floating-point reduction when vectorizing SIMD loops.

Note that these options don't affect auto-vectorization of loops. Please refer to the compiler documentation for more details.

Support Deprecated

Loop Profiler

The Loop Profiler feature is deprecated in the 19.0 compiler and will be removed in a future compiler release. The following compiler options related to Loop Profiler are deprecated and will be removed in a future compiler release: -profile-loops=keyword, -profile-loops-report=value -profile-functions, -guide-profile.

Xcode Integration

Integration with Xcode is deprecated in the 19.0 compiler and will be removed in a future compiler release.

Support Removed

32-bit applications are no longer supported

Starting with the 19.0 release of the Intel® Fortran Compiler, macOS 32-bit applications are no longer supported.
If you want to compile 32-bit applications, you should use an earlier version of the compiler and Xcode* 9.4 or earlier.

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.

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*.

Error 'no rule to process file' within Xcode* 10

macOS*’s new XCode 10 comes with a new build system and it is configured as the default. Currently, the Intel Fortran Compiler does not support it. You will see the error 'no rule to process file' when building an Intel Fortran Compiler project within XCode 10. Please switch to “Legacy Build System” in Project Settings to build your Fortran project in Xcode 10.

For more details please find this article.

Fortran 2008 and Fortran 2018 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 2018 standard. Additional features will be supported in future releases. Features from the proposed Fortran 2018 standard supported by the current version include:

• Assumed type (TYPE(*))
• Assumed rank (DIMENSION(.))
• Relaxed restrictions on interoperable dummy arguments
• C include file ISO_Fortran_binding.h for use by C code manipulating “C descriptors” used by Fortran
• Coarray events
• Intrinsic function coshape
• Default accessibility for entities accessed from a module
• Import Enhancements
• All standard proceduress in ISO_C_BINDING other than C_F_POINTER are now PURE

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, the Intel logo, the Intel Inside logo, Xeon are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.

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

Copyright © 2020 Intel Corporation. All Rights Reserved.

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