Intel® Fortran Compiler

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 Windows* are now available from the Intel Registration Center. You may also receive an email from Intel about this.

Here is what's new in 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. 

Оптимизировали, оптимизировали, да не выоптимизировали!

Оптимизация? Конечно, каждый сталкивался с данной задачей при разработке своих, сколь-нибудь значительных, требующих определённых вычислений, приложений. При этом способов оптимизировать код существует огромное множество, и, как следствие, различных путей сделать это в автоматическом режиме с помощью опций компилятора. Вот здесь и возникает проблема – как выбрать то, что нужно нам и не запутаться?

Intel Parallel Studio XE 2016 Update 1 for Windows - very slow compile time

I have tried compiling a large code under both Visual Studio and Cygwin environments using this FORTRAN compiler.  It is too slow to be usable.  Whereas ifort 12.1(8) took 1-3 seconds per routine this version takes ~5 minutes per routine.  I stopped the build after a few routines.  There is something very wrong with this behavior.  The install went normally after installing VS 2016 and Cygwin.


I came across the following awkward behaviour:

an argument being used in ACOS function displayed in the debugger shows a value 1.00000000000000 but it resulted an a Nan result.

When displayed as hexadecimal,  the argument shows a value #3FF0000000000001.

A PARAMETER initialised to 1.0d+00 displays as  1.00000000000000 and when displayed as hexadecimal shows #3FF0000000000000.

Module variable not recognised in debugger

I want to look at a module variable, so following the documented technique for doing this, in the Watch window I type


The debugger replies that the variable is not recognised, even though the variable is defined as a PARAMETER in the module and calculations up to that point use its value.
The module is in a separate Fortran file. Is that the problem?

I am using VS 2012 Pro.

Suscribirse a Intel® Fortran Compiler