Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Is ifort 2015 available for Linux and OSX?

nousername
Beginner
703 Views

I saw a sticky on the Windows forum that said it has been released though I'm having a hard time figuring out if it's available for Linux/OSX yet. I'm really looking forward to execute_command_line.

0 Kudos
4 Replies
Kevin_D_Intel
Employee
703 Views

Yes it is available for Linux and OS X* also (released simultaneous with the Windows release). You can obtain details about the IPS XE 2015 release here, and for Fortran specific compiler details look here.

With an appropriate license (for either OS) and current support subscription, the IPS XE 2015 downloads should be available under your Intel Premier account.

0 Kudos
TimP
Honored Contributor III
703 Views

I didn't find execute_command_line working for me in the 15.0 release, using the same source code as with gfortran.  Steve Lionel and others discussed this earlier, but I didn't get a sense of what the restrictions are. 

According to the dates on registrationcenter.intel.com,  it's more than a month old.

The 15.0 release on linux did suddenly turn my omp target demonstration into a working one (provided I didn't switch in execute_command_line).

I was able to run the Cluster Studio 15.0 installer after iterating on rpm -qa | grep vtune and rpm -e to get rid of vtune rpmdb entries left from previous versions.  Apparently, although there's no problem adding a new ifort version, the Studio installer can't deal with old vtune entries.  On linux, that's not as severe a block as on Windows.

0 Kudos
Kevin_D_Intel
Employee
703 Views

I think the recent discussion on execute_command_line that Tim is recalling is here. Let us know if there is something further regarding this intrinsic.

0 Kudos
Steven_L_Intel1
Employee
703 Views

We have fixed the bugs we know about in execute_command_line for the first update, planned for late October. If you append a NUL to the command string it avoids the biggest problem.

0 Kudos
Reply