Intel Fortran Compiler 16.0 Update 4 for OS X* Release Notes for Intel Parallel Studio XE 2016

Published: 01/22/2016  

Last Updated: 12/27/2018

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

Change History

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

Changes in Update 4 (Intel® Fortran Compiler 16.0.4)

  • Fixes for reported problems

Changes in Update 3 (Intel® Fortran Compiler 16.0.3)

  • Support for Xcode* 7.3
  • Support for OS X* 10.11.4
  • Fixes for reported problems

Changes in Update 2 (Intel® Fortran Compiler 16.0.2)

  • Support for Xcode* 7.2
  • Fixes for reported problems
  • Documentation updates

Changes in Update 1 (Intel® Fortran Compiler 16.0.1)

Changes since Intel® Fortran Compiler 15.0 (New in Intel® Fortran Compiler 16.0.0)

Back to top

System Requirements

  • An Intel® 64 architecture based Apple* Mac* system
  • 2GB RAM minimum, 4GB RAM recommended
  • 4GB free disk space
  • One of the following combinations of OS X*, Xcode* and the Xcode SDK:
    • OS X 10.10.x, 10.11, 10.11.1, 10.11.2, 10.11.3, 10.11.4, 10.11.5, 10.11.6 and Xcode* 6.x, 7.0, 7.1, 7.2 or 7.3
  • 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.

Back to top

How to use the Intel® Fortran Compiler

The Getting Started Guide at <install-dir>/documentation_2016/ps2016/getstart_comp_of.htm. contains information on how to use the Intel® Fortran Compiler from the command line and from Xcode*.

Back to top

Documentation

Product documentation is linked from <install-dir>/documentation_2016/en/ps2016/getstart_comp_of.htm.

Back to top

Samples

Product samples can be located in the /opt/intel/samples_2016/en/compiler_f/psxe directory.

Back to top

Redistributable Libraries

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

Back to top

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.

Back to top

Compatibility

In general, object code and modules compiled with earlier versions of Intel® Fortran Compiler for OS X* may be used in a build with version 16. Exceptions include:

  • Sources that use the CLASS keyword to declare polymorphic variables and 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.
  • Objects that use the REAL(16) , REAL*16, COMPLEX(16) or COMPLEX*32 datatypes and 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 and were compiled with versions earlier than 11.0 must be recompiled.  The compiler will notify you if this issue is encountered.
  • 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 Fortran compiler cannot be used with version 15.0 or older Fortran compilers.

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

In releases earlier than Intel® Fortran Composer XE 2011 (compiler version 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.0 and later compilers align such items at 16 bytes and expect received arguments to be aligned on 16-byte boundaries.

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.

Back to top

New and Changed Features

Some language features may not yet be described in the compiler documentation. Please refer to the Fortran 2008 Standard (PDF) and the proposed draft Fortran 2015 Standard (PDF) if necessary.

Features from Fortran 2008

  • Submodules
  • IMPURE

Features from the proposed draft Fortran 2015

  • 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

Features from OpenMP* 4.1

The following directives, clauses and procedures, from OpenMP 4.1, are supported by the compiler. For more information, see the compiler documentation or the link to the OpenMP Technical Report.

Intel® 16.0 compiler support for new features in OpenMP* 4.1 draft specification TR3 is subjected to be changed and improved for standard conformance with respect to the official version of the OpenMP* 4.5 specification (to be released in November 2015)

Clauses:

  • SIMDLEN on OMP SIMD directive
  • SIMD on OMP ORDERED directive

New modifiers for omp declare simd linear clause

The linear clause on omp declare simd declarative directive is extended with new modifiers:

           linear (linear-list [ : linear-step] )
           where linear-list is one of the following:
                     list
                     where modifier (list)
                     modifier is one of the following:
                               ref
                               val
                               uval

  • All list items must be dummy arguments of the function that will be invoked concurrently on each SIMD lane.
  • If no modifier is specified or if the val or uval modifier is specified, the value of each list item on each lane corresponds to the value of the list item upon entry to the function plus the logical number of the lane times linear-step.
  • If the uval modifier is specified, each invocation uses the same storage location for each SIMD lane; this storage location is updated with the final value of the logically last lane.
  • If the ref modifier is specified, the storage location of each list item on each lane corresponds to an array at the storage location upon entry to the function indexed
    by the logical number of the lane times linear-step.

New and Changed Directives

The following compiler directives are new or changed in Intel® Parallel Studio XE 2015 Composer Edition – please see the documentation for details:

  • BLOCK_LOOP [ clause [[,] clause...] ]
  • NOBLOCK_LOOP
  • unroll_and_jam (n) [private (var1,[var2]…)]

ATTRIBUTES STDCALL now allowed with BIND(C)

As of compiler version 15.0, the ATTRIBUTES STDCALL directive may be specified for an interoperable procedure (a procedure whose declaration includes the BIND(C) language binding attribute.)

No other effects from STDCALL, such as pass-by-value, are provided. The Fortran standard VALUE attribute (not ATTRIBUTES VALUE) may be used if desired. For all other platforms, specifying STDCALL with BIND(C) has no effect.

New run-time routines to get Fortran library version numbers

  • FOR_IFCORE_VERSION returns the version of the Fortran run-time library (ifcore).
  • FOR_IFPORT_VERSION returns the version of the Fortran portability library (ifport).

Extend uninitialized variable checking using –init=snan to local and heap variables

-init=snan already initializes saved variables of intrinsic numeric type. This is now extended to include local, automatic and allocated variables of intrinsic numeric type.

Back to top

New and Changed Compiler Options

Please refer to the compiler documentation for details.

  • -xCOMMON-AVX512
  • -axCOMMON-AVX512
  • -fpp-name=<name of executable with optional path>
  • -gen-depshow=[no]intr_mod
  • -qopt-prefetch-issue-excl-hint

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

New –xCOMMON-AVX512, -axCOMMON-AVX512 Compiler Options

The COMMON-AVX512 selection has been added for the -x and -ax compiler options. This allows generation of the subset of Intel® Advanced Vector Extensions 512 (Intel® AVX-512) that are supported on both Intel® Many Integrated Core Architecture and on Intel® Core™ Microarchitecture. This includes Intel AVX-512 Foundation instructions and Intel AVX-512 Conflict Detection instructions.

New –fpp-name=<name of executable with optional path> Compiler Option

This new option provides a way for the user to specify a different preprocessor to use with Fortran.

New -gen-depshow=[no]intr_mod Compiler Option

This new option provides a way for the user to exclude intrinsic modules from dependency analysis. It controls whether the intrinsic module dependencies are shown or not. -gen-depshow=nointr_mod is the default.

New -qopt-prefetch-issue-excl-hint Compiler Option

This new option generates PrefetchW instruction for Intel® microarchitecture code name Broadwell processors and beyond, when -qopt-prefetched is also used.

Back to top

Other Changes and Notes

Other Features

For information on these features, please see the compiler documentation.

  • New environment variable INTEL_PROF_DYN_PREFIX. Allows the user to have some control over the naming PGO generated “.dyn” files to make it easy to distinguish files from different runs.  By setting this environment variable to the desired character string prior to starting the instrumented application, the string will be included as prefix to the .dyn file names.
  • The compiler has been changed to give a diagnostic whenever an array constructor without a type specification has different type/kind-type values. For example:
    • (/integer:: 0, 1., 2./) is legal
    • (/0, 1., 2./) is illegal
    • (/real::1., 0, 123, 4./) is legal
    • (/1., 0, 123, 4./) is illegal

Back to top

Known Issues

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

Certain uses of length type parameters in parameterized derived types are not yet fully implemented

The following uses of length type parameters in parameterized derived types (PDTs) are not yet fully implemented:

  • PDT parameter constants with length type parameters
  • %RE and %IM are not yet implemented

OS X* 10.11 Support in Intel® Parallel Studio XE 2016

OS X* 10.11 introduces a new security policy called System Integrity Protection (SIP).  This significantly impacts certain installation scenarios.  Please see OS X* 10.11 Support in Intel® Parallel Studio XE 2016 for important information before attempting to install on OS X* 10.11

Fix included in 16.0 Initial Release to detect an error condition related to User-Defined I/O causes large number of regressions

A fix included in the Intel Fortran Compiler 16.0 initial release to detect an error condition related to User-Defined I/O, DPD200243620 "Missing error for inaccessible components of derived type in I/O list", was found to cause a large number of regressions and has been backed out of the 16.0 Update 1 release.

Back to top

Fortran 2008 and Fortran 2015 Feature Summary

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

  • Maximum array rank has been raised to 31 dimensions (Fortran 2008 specifies 15)
  • CONTIGUOUS attribute
  • MOLD keyword in ALLOCATE
  • DO CONCURRENT
  • NEWUNIT keyword in OPEN
  • G0 and G0.d format edit descriptor
  • Unlimited format item repeat count specifier
  • A CONTAINS section may be empty
  • Intrinsic procedures BESSEL_J0, BESSEL_J1, BESSEL_JN, BESSEL_YN, BGE, BGT, BLE, BLT, DSHIFTL, DSHIFTR, ERF, ERFC, ERFC_SCALED, GAMMA, HYPOT, IALL, IANY, IPARITY, IS_CONTIGUOUS, LEADZ, LOG_GAMMA, MASKL, MASKR, MERGE_BITS, NORM2, PARITY, POPCNT, POPPAR, SHIFTA, SHIFTL, SHIFTR, STORAGE_SIZE, TRAILZ,
  • Additions to intrinsic module ISO_FORTRAN_ENV: ATOMIC_INT_KIND, ATOMIC_LOGICAL_KIND, CHARACTER_KINDS, INTEGER_KINDS, INT8, INT16, INT32, INT64, LOCK_TYPE, LOGICAL_KINDS, REAL_KINDS, REAL32, REAL64, REAL128, STAT_LOCKED, STAT_LOCKED_OTHER_IMAGE, STAT_UNLOCKED
  • An OPTIONAL dummy argument that does not have the ALLOCATABLE or POINTER attribute, and which corresponds to an actual argument that: has the ALLOCATABLE attribute and is not allocated, or has the POINTER attribute and is disassociated, or is a reference to the intrinsic function NULL, is considered not present
  • A dummy argument that is a procedure pointer may be associated with an actual argument that is a valid target for the dummy pointer, or is a reference to the intrinsic function NULL.  If the actual argument is not a pointer, the dummy argument shall have the INTENT(IN) attribute.
  • BLOCK construct
  • intrinsic subroutine EXECUTE_COMMAND_LINE
  • Submodules
  • IMPURE

Proposed draft Fortran 2015 features 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

Coarrays are not supported on OS X.

Back to top

Disclaimer and Legal Information

Optimization Notice

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804

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: 

http://www.intel.com/products/processor%5Fnumber/

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 © 2016 Intel Corporation. All Rights Reserved.

Back to top

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.