Intel® Fortran Compiler

Join the Intel® Parallel Studio XE 2018 Beta program

We would like to invite you to participate in the Intel® Parallel Studio XE 2018 Beta program. In this beta test, you will gain early access to new features and analysis techniques. Try them out, tell us what you love and what to improve, so we can make our products better for you. 

Registration is easy. Complete the pre-beta survey, register, and download the beta software:

Intel® Parallel Studio XE 2018 Pre-Beta survey

Join the Intel® Parallel Studio XE 2018 Beta program

We would like to invite you to participate in the Intel® Parallel Studio XE 2018 Beta program. In this beta test, you will gain early access to new features and analysis techniques. Try them out, tell us what you love and what to improve, so we can make our products better for you. 

Registration is easy. Complete the pre-beta survey, register, and download the beta software:

Intel® Parallel Studio XE 2018 Pre-Beta survey

PSXE 2017 Update 2 - Internal Compiler Error(s) involving PARAMETER constants and /debug-parameters /debug options

PSXE 2017 Update 2 - Internal Compiler Error(s) involving PARAMETER constants and /debug-parameters /debug options

A defect (regression) has been found in the Intel® Parallel Studio XE 2017 Update 2 (17.0 compiler) release involving the use of PARAMETER constants along with the /debug-parameter and /debug options. The combined use can led to multiple internal compiler errors.

The following example (complements of andrew_4619) demonstrates usage that will trigger the internal error:

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.

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

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

Request to issue an error with a deleted/removed feature when /warn:stderrors compiler option is in effect.

Starting with FORTRAN 77 (ANSI X3.9 1978), the so-called "extended range of a DO loop" feature has been removed.  However when an example code involving this feature is compiled using Intel Fortran with /warn:stderrors but no /f66 option, no error is issued.  Can the Intel Fortran team consider a change where an error will be issued under such a circumstance?

Подписаться на Intel® Fortran Compiler