Intel® Fortran Compiler for Linux* and Mac OS X*

The Intel® Parallel Studio XE 2016 Update 1 is now available

All editions (Cluster, Professional, Composer) of the Intel® Parallel Studio XE 2016 Update 1 for Linux* and OS X*are now available from the Intel Registration Center. You may also receive an email from Intel about this.

Here is what's new the Intel® Parallel Studio XE 2016 Update 1 release.

OS X 10.9 Xcode 5 error ld: library not found for -lcrt1.10.6.o

Environment:  OS X 10.9 (Mavericks) and Xcode 5.0

Command line compilations/links fail with "ld: library not found for -lcrt1.10.6.o"

Affected compiler:  Intel Composer XE 2013 Update 1

Root cause:  Xcode 5.0 installation does not install all command line tools (include files, libraries, SDKs) need for the compiler to link user applications. 

Compiler optimization reports

I was wondering if there is (or there are plans for) a feature built in to the Intel compilers that would combine compiler optimization reports with source code listings, as with the VecAnalysis script provided by Intel.  That script is really handy, but unfortunately it does not seem to work with anything later than the 13.1 compiler release.  This script makes the vectorization and other reports much more understandable.

Mac OS X installer problem

So, I downloaded the latest installer image <m_fcompxe_2016.1.043.dmg>. Installed the latest Xcode (7.1.1) and also the command line developer tools. Then opened the Intel Fortran installer image and launched the installer application <>. I was logged in as Administrator, and am running OS X El Capitan 10.11.1. I have a valid product serial number for Intel® Parallel Studio XE Composer Edition for Fortran OS X*. The installer application provided a screen to select between two options: 1. Install as Administrator. 2. Install as root.

Are there any known problems with Intel compiler?


Hello sir,


Now I am coding with PGI compiler but I am reviewing change my compiler to Intel Fortran from PGI, Are there any known problems or issues when I compile with my legacy source codes? If it is, could you provide that issues and how to resolve it?

Thanks in advance.

Intel series 16 FC lead to segmentation faults and inaccurate numerics in VASP 5.4 (intel 15 series works fine)

I would like to mention that VASP 5.4.1 compiled using intel compilers lead to segmentation faults (i.e. with electric fields), and/or inaccurate numerics (i.e. with GW). Reducing the optimization level from the default -o2 to -o1, even -o0 does not help.

The same VASP scenarios, using intel 15 compilers, run without any segmentation faults, or numerical drifts.

Is there a way to replicate intel 15 like behaviour in 16?


Intel® Fortran Compiler for Linux* and Mac OS X* abonnieren