Intel® Fortran Compiler

Inconsistent program behavior on RHEL* 7.4 or Fedora* 25 if compiled with Intel Compiler

We've seen some reports with regarding to RHEL7.4 OS and Fedora 25 that comes with glibc that has a change that Intel Compiler doesn't work well with. There're simple workarounds for the problem. Please see the following two KB articles for details.

Intel® Parallel Studio XE 2018 has been released!

Intel® Parallel Studio XE 2018, including Intel® Fortran Compiler 18.0, is now available from the Intel Registration Center. Release notes can be found here.

The Intel® Fortran Compiler now supports all features from the Fortran 2008 standard. Additional Fortran 2008 features added in the Intel® Fortran 18.0 release are noted below:
 

rc.exe not found

I have a piece of code that runs on another computer that I'm trying to compile and run on my computer but whenever I try to build the solution I get an error rc.exe not found. I've done some research and believe that the issue is related to having the wrong combination of Visual Studio and Intel Fortran installed together. I've tried uninstalling and reinstalling several different version of both VS and Parallel Studio, ranging from 2013 - 2017 but I have not had much luck.

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

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

BIND (C) clause error

Hello,

I upgraded the IVF Compiler to 17.0.5.267 and now one of my projects won't compile. I get the following error: "Error: A dummy procedure must not be specified with a NAME=Specifier".

My code is doing using the BIND (c) clause just like this: SUBROUTINE CSub () BIND(C, NAME="CSub)

​Is there a new way of doing this in this compiler version? Sorry if the question doesn't make much sense. I am fairly new to Fortran :)!

 

ifort: error #10273: Fatal error in C:\PROGRA~2\INTELS~1\COMPIL~3\windows\bin\intel64\fortcom, terminated by 0xc0000417

The last couple of days I have been getting a few ifort: error #10273: Fatal error in C:\PROGRA~2\INTELS~1\COMPIL~3\windows\bin\intel64\fortcom, terminated by 0xc0000417.  The pattern is random, the source files will compile OK if I retry.  Maybe this is a symptom of a problem on the PC, e.g. AV/memory etc..... but I don't have problems with anything else on the PC.  It is not a big problem but any thoughts, suggestion?

Doctor Fortran in "Eighteen is the new Fifteen"

When the international Fortran standards committee (WG5) met in 2012 to set a schedule for the next standard revision, the informal name of the standard was set to be "Fortran 2015". The schedule changed over the subsequent years, but the name stayed the same. The current schedule has the standard being published in the second half of 2018, which caused a question to be asked: "Should we perhaps think of changing the year number to something more current?"
Subscribe to Intel® Fortran Compiler