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

The Intel® Parallel Studio XE 2016 Update 1 is now available

Kevin_D_Intel
Employee
2,006 Views

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.

Additional compiler details are available in the Intel® Fortran Compiler 16.0 Release Notes.

There are known issues with updating using the Intel Software Manager for Windows*. Please refer to the article, Intel® Parallel Studio XE 2016 update 1 for Windows* - Issues updating via Intel Software Manager, for details and workarounds.

0 Kudos
8 Replies
Johannes_Rieke
New Contributor III
2,006 Views

Thanks for the info.

I installed 16.0.1.146 parallel to 16.0 Fortran compilers some minutes ago. Two issues with VS2015 occured:

1st.: VS2015->Tools->options->Intel Compilers and Tools -> Visual Fortran -> Compilers -> selected compilers -> latest points still to 16.0 and not to 16.0.1. I had to change this manually to 16.0.1

2nd: wrong path to libucrt.lib etc. Maybe C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10156.0 ist not installed by the installer? On my computer I only have ...Lib\10.0.10150.0. So I have to manually edit the path in VS2015->Tools->options->Intel Compilers and Tools -> Visual Fortran -> Compilers -> selected compilers -> Libraries. This happened before in 15.0.5 where VS2015 firstly was supported. Unless you change this, linking will fail...

So far a quick check.

Best regards, Johannes

EDIT: as Andrew Win 7 Prof. SP1

0 Kudos
Andrew_Smith
Valued Contributor I
2,006 Views

Johannes wrote:

Thanks for the info.

I installed 16.0.1.146 parallel to 16.0 Fortran compilers some minutes ago. Two issues with VS2015 occured:

1st.: VS2015->Tools->options->Intel Compilers and Tools -> Visual Fortran -> Compilers -> selected compilers -> latest points still to 16.0 and not to 16.0.1. I had to change this manually to 16.0.1

2nd: wrong path to libucrt.lib etc. Maybe C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10156.0 ist not installed by the installer? On my computer I only have ...Lib\10.0.10150.0. So I have to manually edit the path in VS2015->Tools->options->Intel Compilers and Tools -> Visual Fortran -> Compilers -> selected compilers -> Libraries. This happened before in 15.0.5 where VS2015 firstly was supported. Unless you change this, linking will fail...

So far a quick check.

Best regards, Johannes

Same for me. Using Windows 7 Professional, SP1

0 Kudos
TimP
Honored Contributor III
2,006 Views

My update installation did add a new set of shortcuts to the updated version, using the 10150\ucrt, but I still see the link time failure for the VS2015 cmd window:

LINK : fatal error LNK1104: cannot open file 'kernel32.lib'

Also, CL doesn't have the 10150\ucrt path when running in the Intel cmd window.  I guess it requires adding a -I specifier.

I didn't understand from the description above where you found the place to edit the VS2015 default librarie paths selection.

I link successfully under the VS2013 environment, using -Qlocation,link to point to the VS2015 linker, although some .obj must be built with the previous ifort release, due to a new ICE (which can be avoided by removing Qopt-report or not using AVX).  So it doesn't appear that VS2015 lacks the .lib files.  The VS2013 environment doesn't accept .obj built under VS2015 even though the VS2015 link is in use.

I guess it's fortunate that the installer didn't want to replace ifort but instead made the side-by-side installation.

The update installation proceeded without hitches in the VS2012/13 integrations and on linux, all within 3 hours.  Performance improvements came in Cilk(tm) Plus CEAN.

If someone would notify us if any updates are wanted when Premier problem report site may be brought back on line, it would be relatively little additional effort from me.  What's annoying is to have nearly completed a submission and then the site fails to take it.

0 Kudos
TimP
Honored Contributor III
2,006 Views

After further communication from Intel support, it appears that a working installation at Intel using windows kits\10\ 10150 is also using windows kits\8.1\ to fill in the missing .lib references.  Possibly due to having VS2012 and 2013 installed and working, my VS2015 installation is not looking at the 8.1 references.  Further reading of Microsoft known problems etc. turns up a recommendation to clean out all Visual Studio installations before installing (or updating?) VS2015.

There is a  Microsoft windows kits\10\ 10240 release (re-released in Sept. 2015) which appears to be self contained, so that it would not require references to \8.1\.

Specifically, for example, copying windows kits\10\lib\10.0.10240.0\um into \lib\10.0.10150.0  takes care of kernel32.lib.  Running a repair on VS2015 after running the new sdksetup.exe also works; then VS2015 appears to be switched entirely to the updated windows kits.

Copying windows kits\10\include\10.0.10240.0\ucrt\float.h to microsoft visual studio 14.0\vc\include\ takes care of the Intel paths directing CL to look only in the original location.  After repair, Visual Studio outside of Intel environment setting doesn't require this copy of include file to the old location.

Intel support pointed out that the Microsoft provided file vcvarsqueryregistry.bat controls which path entries are set before the Intel setup begins.  I might conclude that Microsoft supports it only for the case of the clean installation of VS2015 alone (from scratch, not by updating in place).

0 Kudos
TimP
Honored Contributor III
2,006 Views

The new ICE comes up with the combination of -Qopt-report, -QxAVX, and no setting of old_maxminloc.  Apparently, the default setting has changed to -assume:noold_maxminloc (preventing vectorization).  With -assume:old_maxminloc, update 1 appears to work the same as update 0, including efficient vectorization of rank 1 maxloc.

I still wonder why f2003 compliant maxloc/minloc should be so troublesome, particularly if it's only a question of the result returned for a 0-length array section.

0 Kudos
tiho
Beginner
2,006 Views

After I installed the update I get this error messages and can't compile

1>IntelDev : error PRJ0019: A tool returned an error codetranpa.for
1>IntelDev : error PRJ0019: A tool returned an error codesprod.for
1>IntelDev : error PRJ0019: A tool returned an error codereov21.for
1>IntelDev : error PRJ0019: A tool returned an error codesetstp97.for

....

Any idea?

 

0 Kudos
tiho
Beginner
2,006 Views

The above problem happens just for 64 bit compilation. With the 32 bit compilation, I can compile however however I get a link error

1>Linking...
1>LINK : fatal error LNK1104: cannot open file 'libiompstubs5md.lib' 

I am using Windows 10 with VS2013 integrated shell

0 Kudos
Steven_L_Intel1
Employee
2,006 Views

Please uninstall Intel Parallel Studio XE and then reinstall and see if that solves the problem. If not, please start a NEW topic here and describe the issue.

0 Kudos
Reply