1. Intel C++ Compiler Price
2. Intel C++ Compiler Free
3. Download Intel C++ Compiler

By HD86 New User in Intel® C Compiler. Intel VTune community download. By trafalco New User in Analyzers. Using OpenVinotoolkit with Anaconda Environment on windows 10. By DeepakMahtani25 Beginner in Intel® Distribution of OpenVINO™ Toolkit.

1. C compiler for mac free download. Small Device C Compiler SDCC is a retargettable, optimizing standard C (ANSI C89 / ISO C90, ISO C99, ISO C11 / C17) compiler.
2. Intel C Compiler Professional Edition delivers rapid development and winning performance for the full range of Intel processor-based platforms.
3. With the Intel® C Compiler, you can create code that takes advantage of more cores and built-in technologies in platforms based on Intel® processors. Compile and generate applications for Windows., Linux., and macOS.
4. Steps to install icpc (Intel C/C compiler) on Mac OS X and run a simple OpenMP program. Tested with OS X Yosemite. pramttl/installing-icpc-osx. Steps to install icpc (Intel C/C compiler) on Mac OS X and run a simple OpenMP program. I got an email with the serial key and a download link. There were multiple download options.
5. Download and install the best free apps for Interpreters & Compilers on Windows, Mac, iOS, and Android from CNET Download.com, your trusted source for the top software picks.

Intel C++ Compiler, also known as icc or icl, is a group of C and C++compilers from Intel available for Windows, Mac, Linux, FreeBSD^[3] and Intel-based Android devices.

Overview[edit]

The compilers generate optimized code for IA-32 and Intel 64 architectures, and non-optimized code for non-Intel but compatible processors, such as certain AMD processors. A specific release of the compiler (11.1) is available for development of Linux-based applications for IA-64 (Itanium 2) processors.

The 14.0 compiler added support for Intel-based Android devices and optimized vectorization and SSE Family instructions for performance. The 13.0 release added support for the Intel Xeon Phi coprocessor. It continues support for automatic vectorization, which can generate SSE, SSE2, SSE3, SSSE3, SSE4, AVX and AVX2SIMD instructions, and the embedded variant for Intel MMX and MMX 2.^[4] Use of such instruction through the compiler can lead to improved application performance in some applications as run on IA-32 and Intel 64 architectures, compared to applications built with compilers that do not support these instructions.

Intel compilers support Cilk Plus (removed in 19.1), which is a capability for writing vectorized and parallel code that can be used on IA-32 and Intel 64 processors or which can be offloaded to Xeon Phi coprocessors. They also continue support for OpenMP 4.0, symmetric multiprocessing, automatic parallelization, and Guided Auto-Parallization (GAP). With the add-on Cluster OpenMP capability, the compilers can also automatically generate Message Passing Interface calls for distributed memory multiprocessing from OpenMP directives.

Intel C++ is compatible with Microsoft Visual C++ on Windows and integrates into Microsoft Visual Studio. On Linux and Mac, it is compatible with GNU Compiler Collection (GCC) and the GNU toolchain. Intel C++ Compiler for Android is hosted on Windows, OS X or Linux and is compatible with the Android NDK, including gcc and the Eclipse IDE. Intel compilers are known for the application performance they can enable as measured by benchmarks, such as the SPEC CPU benchmarks.

Optimizations[edit]

Intel compilers are optimized to computer systems using processors that support Intel architectures. They are designed to minimize stalls and to produce code that executes in the fewest possible number of cycles. The Intel C++ Compiler supports three separate high-level techniques for optimizing the compiled program: interprocedural optimization (IPO), profile-guided optimization (PGO), and high-level optimizations (HLO). The Intel C++ compiler in the Parallel Studio XE products also supports tools, techniques and language extensions for adding and maintaining application parallelism on IA-32 and Intel 64 processors and enables compiling for Intel Xeon Phi processors and coprocessors.

Profile-guided optimization refers to a mode of optimization where the compiler is able to access data from a sample run of the program across a representative input set. The data would indicate which areas of the program are executed more frequently, and which areas are executed less frequently. All optimizations benefit from profile-guided feedback because they are less reliant on heuristics when making compilation decisions.

High-level optimizations are optimizations performed on a version of the program that more closely represents the source code. This includes loop interchange, loop fusion, loop fission, loop unrolling, data prefetch, and more.^[5]

Interprocedural optimization applies typical compiler optimizations (such as constant propagation) but using a broader scope that may include multiple procedures, multiple files, or the entire program.^[6]

David Monniaux has criticized Intel's compiler for applying, by default, floating-point optimizations which are not allowed by the C standard and which require special flags with other compilers such as gcc.^[7]

Architectures[edit]

• x86-64 (Intel 64 and AMD64)
• IA-64 (Itanium 2)

Description of packaging[edit]

Except for the Intel Bi-Endian C++ Compiler, Intel C++ compilers are not available in standalone form. They are available in suites:

• Intel Parallel Studio XE for development of technical, enterprise, and high-performance computing applications on Windows, Linux and Mac
• Intel System Studio for development of system and app software for embedded systems or devices running Windows, Linux or Android

The suites include other build tools, such as libraries, and tools for threading and performance analysis.

History since 2003[edit]

Flags and manuals[edit]

Documentation can be found at the Intel Software Technical Documentation site.

Debugging[edit]

The Intel compiler provides debugging information that is standard for the common debuggers (DWARF 2 on Linux, similar to gdb, and COFF for Windows). The flags to compile with debugging information are /Zi on Windows and -g on Linux. Debugging is done on Windows using the Visual Studio debugger and, on Linux, using gdb.

While the Intel compiler can generate a gprof compatible profiling output, Intel also provides a kernel level, system-wide statistical profiler called Intel VTune Profiler. VTune can be used from a command line or thru an included GUI on Linux or Windows. It can also be integrated into Visual Studio on Windows, or Eclipse on Linux). In addition to the VTune profiler, there is Intel Advisor that specializes in vectorization optimization, offload modeling, flow graph design and tools for threading design and prototyping.

Intel also offers a tool for memory and threading error detection called Intel Inspector XE. Regarding memory errors, it helps detect memory leaks, memory corruption, allocation/de-allocation of API mismatches and inconsistent memory API usage. Regarding threading errors, it helps detect data races (both heap and stack), deadlocks and thread and synch API errors.

Reception[edit]

Intel and third parties have published benchmark results to substantiate performance leadership claims over other commercial, open-source and AMD compilers and libraries on Intel and non-Intel processors. Intel and AMD have documented flags to use on the Intel compilers to get optimal performance on Intel and AMD processors.^[11][12] Nevertheless, the Intel compilers have been known to use sub-optimal code for processors from vendors other than Intel. For example, Steve Westfield wrote in a 2005 article at the AMD website:^[13]

Intel 8.1 C/C++ compiler uses the flag -xN (for Linux) or -QxN (for Windows) to take advantage of the SSE2 extensions. For SSE3, the compiler switch is -xP (for Linux) and -QxP (for Windows). ... With the -xN/-QxN and -xP/-QxP flags set, it checks the processor vendor string—and if it's not 'GenuineIntel', it stops execution without even checking the feature flags. Ouch!

The Danish developer and scholar Agner Fog wrote in 2009:^[14]

The Intel compiler and several different Intel function libraries have suboptimal performance on AMD and VIA processors. The reason is that the compiler or library can make multiple versions of a piece of code, each optimized for a certain processor and instruction set, for example SSE2, SSE3, etc. The system includes a function that detects which type of CPU it is running on and chooses the optimal code path for that CPU. This is called a CPU dispatcher. However, the Intel CPU dispatcher does not only check which instruction set is supported by the CPU, it also checks the vendor ID string. If the vendor string is 'GenuineIntel' then it uses the optimal code path. If the CPU is not from Intel then, in most cases, it will run the slowest possible version of the code, even if the CPU is fully compatible with a better version.

This vendor-specific CPU dispatching (function multi-versioning) decreases the performance on non-Intel processors of software built with an Intel compiler or an Intel function library – possibly without the knowledge of the programmer. This has allegedly led to misleading benchmarks,^[14] including one incident when changing the CPUID of a VIA Nano significantly improved results.^[15] A legal battle between AMD and Intel over this and other issues has been settled in November 2009.^[16] In late 2010, AMD settled a US Federal Trade Commissionantitrust investigation against Intel.^[17]

The FTC settlement included a disclosure provision where Intel must:^[18]

publish clearly that its compiler discriminates against non-Intel processors (such as AMD's designs), not fully utilizing their features and producing inferior code.

In compliance with this rule, Intel added an 'optimization notice' to its compiler descriptions stating that they 'may or may not optimize to the same degree for non-Intel microprocessors' and that 'certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors'. It says that:^[19]

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.

As reported by The Register^[20] in July 2013, Intel was suspected of 'benchmarksmanship', when it was shown that the object code produced by the Intel compiler for the AnTuTu Mobile Benchmark omitted portions of the benchmark which showed increased performance compared to ARM platforms.

See also[edit]

• Intel Integrated Performance Primitives (IPP)
• Intel Data Analytics Acceleration Library (DAAL)
• Intel Math Kernel Library (MKL)
• Intel Threading Building Blocks (TBB)
• VTune Amplifier
• Intel Developer Zone (Intel DZ; support and discussion)

References[edit]

1. ^'Intel C++ Compiler 19.1 Release Notes'.
2. ^'Intel C++ Compiler for Android documentation'.
3. ^'Intel® System Studio 2016 for FreeBSD* | Intel® Software'. software.intel.com. Retrieved 2018-03-15.
4. ^A. J. C. Bik, The Software Vectorization Handbook (Intel Press, Hillsboro, OR, 2004), ISBN0-9743649-2-4.
5. ^The Software Optimization Cookbook, High-Performance Recipes for IA-32 Platforms, Richard Gerber, Aart J.C. Bik, Kevin B. Smith, and Xinmin Tian, Intel Press, 2006
6. ^Intel C++ Compiler XE 13.0 User and Reference Guides
7. ^The pitfalls of verifying floating-point computations, by David Monniaux, also printed in ACM Transactions on programming languages and systems (TOPLAS), May 2008; section 4.3.2 discusses nonstandard optimizations.
8. ^This note is attached to the release in which Cilk Plus was introduced. This ULR points to current documentation: http://software.intel.com/en-us/intel-composer-xe/
9. ^Intel C++ Composer XE 2013 Release Notes[1]http://software.intel.com/en-us/articles/intel-c-composer-xe-2013-release-notes/
10. ^'Intel® Compilers | Intel® Developer Zone'. Intel.com. 1999-02-22. Retrieved 2012-10-13.
11. ^[2]Archived March 23, 2010, at the Wayback Machine
12. ^'Archived copy'(PDF). Archived from the original(PDF) on 2011-03-22. Retrieved 2011-03-30.CS1 maint: archived copy as title (link)
13. ^'Your Processor, Your Compiler, and You: The Case of the Secret CPUID String'. Archived from the original on 2012-01-05. Retrieved 2011-12-11.
14. ^ ^ab'Agner`s CPU blog - Intel's 'cripple AMD' function'. www.agner.org.
15. ^Hruska, Joel (29 July 2008). 'Low-end grudge match: Nano vs. Atom'. Ars Technica.
16. ^'Settlement agreement'(PDF). download.intel.com.
17. ^'Intel and U.S. Federal Trade Commission Reach Tentative Settlement'. Newsroom.intel.com. 2010-08-04. Retrieved 2012-10-13.
18. ^'FTC, Intel Reach Settlement; Intel Banned From Anticompetitive Practices'. Archived from the original on 2012-02-03. Retrieved 2011-10-20.
19. ^'Optimization Notice'. Intel Corporation. Retrieved 11 December 2013.
20. ^'Analyst: Tests showing Intel smartphones beating ARM were rigged'.

External links[edit]

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 3

• Not applicable for macOS

NOTE: Intel® Parallel Studio XE 2020 Composer Edition for Fortran and C++ Linux* contains an update to the Intel® C++ Compiler next generation code generator. This is invoked using the -qnextgen option to the ICC and ICPC compilers. This update to the Intel® C++ Compiler next generation code generator includes our latest updates and features for our C++ next generation compiler invoked with the -qnextgen option.

• There are no new features, bug fixes, or security enhancements for the Intel® Fortran Compiler or the Intel® C++ Compiler without the -qnextgen option.
• Intel® Parallel Studio XE 2020 Update 3 is available for the Intel® Parallel Studio XE 2020 Composer Edition for Fortran and C++ Linux*.
• This is a Linux-only release: there is no Update 3 release for either Windows* or macOS* operating systems.
• In addition, it is only a Composer Edition release: there is no Update 3 release for either Professional or Cluster Editions of Intel® Parallel Studio XE 2020.
• There is no update to the Intel® C++ and Fortran Compilers Redistributable Libraries. The Update 2 versions of these libraries are compatible and should be used.
• There is no update for the Intel® Parallel Studio XE Runtime 2020 YUM* and APT* repository packages. Continue to use the Update 2 packages of this runtime.

Changes in Update 2 (Intel® Fortran Compiler 19.1.2)

• Corrections to reported problems.

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

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

Intel C++ Compiler Price

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

This article explains which version of Xcode* is supported by Intel Fortran Compiler release.

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

Intel C++ Compiler Free

• 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.-m[no-]branches-within-32B-boundaries

-m[no-]branches-within-32B-boundaries

Support Deprecated

The compiler option -stand f15 will be removed in next update. Use -stand f18 instead.

GNU* DBG support will be removed in the next update.

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.

Download Intel C++ Compiler

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.