Composer XE Fortran Intel®

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

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

XE 2015 update 4 install on Vista?


Apologies if this has been covered before but it is a while (ex 2013) since I updated my compiler.  Email for latest update came a day or so ago and I figured it was about time I updated from XE2013 (has mostly been working fine, but have been encountering some issues of late).

Anyway, at the very start of the install process I get the following message:

Thread safe Fortran

I'm working on making an existing fortran library thread safe. I do this by setting copiler options: /recursive, /reentrancy:threaded, /threads and /Qauto, and by not writing to global variables. I am also in the process of removing data-initialized variables, as these seem to implicitly declared as SAVE. Anything else I need to think about?

Edit source while running in Debug mode

I am running VS 2013 V 12.0.21005.1 and 2015 Composer Fortran for Windows (Package 2015.0.108).  I just installed in on a new computer and moved a solution and related projects and source from an existing older computer.  On the old computer, I am able to Edit source code while running a program.  I usually continue editing (while running in debug) until the line numbers get "lost", then I restart the program and continue.  On the new computer, all files are locked as soon as I start running in debug mode and I cannot edit even at a break point or by using break all.

How to resolve internal error when compiling existing Fortran solution? (BuildLog.htm reproduced)

I have a Fortran solution which compiled without problem using IVF in MSVS 2010 Professional. Unfortunately I cannot use 2010 anymore to compile due to some IT problem. Instead they have given me MSVS 2008 with IVF. I copied all the files in the existing solution into a new folder and opened up the solution file in 2008. I elected to clean and rebuild the solution.


On rebuild I get the following error (reproduced below from BuildLog.htm) which causes the compilation to abort:

XE 2015 update 4 ( some tutorials are gone

Dear Intel team,

I got the message that XE 2015 update 4 is available and installed it over the existing update 3. After installing update 4 ...\Intel\Composer XE 2015\Samples\en_US\mkl contains two zips (,, see attachment) which are empty. At version there was only one zip (, which contains sample code in C and Fortran. I'm a little bit confused by the two empty zips. Should it look like this? In the MKL directory the other examples are still present.

Intel Software Manager Problem

In the software manager licences tab all my products say "Support expired on 5th April 2015". All the latest versions are thus not available to download.  If I click the renew link which takes me to the registration centre we have "Your Support service is active till 06 Apr 2016 " for the same products ( and yes I did part with cash before the expiry date!).  How do I fix this?

BTW I can download directly from the registration centre with no problem, it is just that is is better if the licence manager manages!



Assine o Composer XE Fortran Intel®