Please see the licenses included in the distribution as well as the Disclaimer and Legal Information section of these release notes for details. Please see the following links for information on this release of the Intel® Visual Fortran Compiler 19.0.
This section highlights important changes from the previous product version and changes in product updates.
This is release for Intel® Compilers 2019 Update 8, compilers version 19.0.8. Highlights for this release:
This is release 2019 Update 5, compiler version 19.0.5. Highlights for this release:
This is the final release of 2019 Update 4.
This is the initial release of 2019 Update 4. This was released in Linux* and Windows* packages only (no macOS* release).
This compiler is only available in the Intel® Registration Center in packages for:
This version provided initial support for VS2019 Integrations and includes certain functional and security updates. We recommend updating for these functional and security updates. "Update 4 Eng/Jpn" build should be used as it is the latest Update 4 compiler (see above). If you are macOS* user there was no "initial" compiler release (see Update 4 Eng/Jpn above).
These packages contain both the Intel® C++ Compiler and the Intel® Fortran Compiler. During installation you can select one or both compilers using the CUSTOM installation options.
For your next steps, use this table and the notes that follow the table:
Changes in this version:
Intel® Visual Fortran Compiler 19.0 for Windows* initial release includes the following components:
For an explanation of architecture names, see Intel® Architecture Platform Terminology
Installation instructions are shipped with all Intel® Software Development Products as part of the documentation.
Installation guides for the latest Intel® Parallel Studio XE version are also available online. Please check Intel® Parallel Studio XE getting started page for installation guides. Note that link to Installation Guide is also available on Intel® Registration Center while downloading required installation package. Please refer to Installation FAQ for more details.
Intel® Parallel Studio XE 2019: Getting Started with the Intel® Fortran Compiler 19.0 for Windows* at <install-dir>\IntelSWTools\documentation_2019\en\compiler_f\ps2019\getstart_wf.htm contains information on how to use the Intel® Visual Fortran Compiler from the command line and from Microsoft Visual Studio*.
Product documentation is linked from<install-dir>\IntelSWTools\documentation_2019\en\compiler_f\ps2019\getstart_wf.htm.
Offline core documentation is removed from the Intel® Parallel Studio XE installed image. The core documentation for the components of Intel® Parallel Studio XE are available at the Intel® Software Documentation Library for viewing online. You may also access the documentation online by following the links from the Getting Started Guide, which can be viewed from the help menu.
Please use the instructions from this article to add Intel® Compiler documentation to your local machine.
Refer to the Intel® Parallel Studio XE Support – Documentation for additional User and Reference Guides, What’s New and Release Notes, and Installation Guides.
Documentation on using QuickWin, dialogs and the Windows API is available from the Intel Software Documentation Library: See Using Intel® Visual Fortran to Create and Build Windows*-based Applications (PDF)
If on Windows Server 2012 you find that you cannot display help or documentation from within Internet Explorer 10, modifying a security setting for Microsoft Internet Explorer usually corrects the problem. From Tools > Internet Options > Security, add “about:internet” to the list of trusted sites. Optionally, you can remove “about:internet” from the list of trusted sites after you finish viewing the documentation.
When viewing Intel compiler documentation with the Microsoft Edge* browser on a Japanese version of Microsoft Windows 10*, the upper left corner [Content][Index][Search] buttons do not function properly. Clicking on any of the buttons results in a blank screen.
The issue will be fixed in a future release. To workaround the issue, use Internet Explorer to view the Intel compiler documentation. To set your default browser to Internet Explorer, Google search "how to make Internet Explorer default browser on Windows 10".
The Visual Studio* internal browser default mode may cause multi-pane documents to not display correctly. The table of contents appears in the left pane, but the right pane does not display any content. The alternative is to access the same documentation from the Visual Studio* Help menu.
Intel®-provided debug solutions are based GNU* GDB. Please see Intel® Parallel Studio 2019 Composer Edition Fortran - Debug Solutions Release Notes for further information.
Japanese language support is not provided with this release of the product.
Product samples are now available online at Intel® Software Product Samples and Tutorials.
Refer to the Redistributable Libraries for Intel® Parallel Studio XE for more information.
If you did not register your compiler during installation, please do so at the Intel® Software Development Products Registration Center. Registration entitles you to free technical support, product updates and upgrades for the duration of the support term.
For information about how to find Technical Support, Product Updates, User Forums, FAQs, tips and tricks, and other support information, please visit http://www.intel.com/software/products/support/
Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.
In general, object code and modules compiled with earlier versions of Intel Fortran Compiler (8.0 and later) may be used in a build with version 19.0. Exceptions include:
In previous releases, when a REAL(16) or COMPLEX(16) (REAL*16 or COMPLEX*32) item was passed by value, the stack address was aligned at 4 bytes. For improved performance, compiler versions 12.0 and later align such items at 16 bytes and expect received arguments to be aligned on 16-byte boundaries.
This change primarily affects compiler-generated calls to library routines that do computations on REAL(16) values, including intrinsics. If you have code compiled with earlier versions and link it with the version 13 libraries, or have an application linked to the shared version of the Intel run-time libraries, it may give incorrect results.
In order to avoid errors, you must recompile all Fortran sources that use the REAL(16) and COMPLEX(16) datatypes.
The static form of the Intel® OpenMP* library, libiomp5mt.lib, is no longer provided, and the /Qopenmp-link:static command line option is no longer supported. Please replace all references to libiomp5mt.lib with libiomp5md.lib, the DLL import library. This change also implies that applications using OpenMP will need to have the Intel® compiler redistributables installed if deployed on a system where an Intel® compiler is not also present. See Redistributable Libraries for Intel® Parallel Studio XE for more information.
Fortran Expression Evaluator (FEE) is a plug-in for Microsoft Visual Studio* that is installed with Intel® Visual Fortran Compiler. It extends the standard debugger in Microsoft Visual Studio* IDE by handling Fortran expressions. There is no other change in usability.
The Intel® Fortran Compiler supports all features from the Fortran 2008 standard.
The Intel® Software License Manager has been updated to version 2.9 for this release. You must upgrade to this version before installing Intel Parallel Studio XE 2019 Update 4 with a floating license. Please refer for more details:
Please refer to the compiler documentation for details.
For a list of deprecated compiler options, see the Compiler Options section of the documentation.
These switches tell the compiler to produce errors or warnings when shapes of arrays do not match on assignments. This check is done for assignments only (and implicit assignments resulting from an allocate with source= syntax).
/Qopenmp-simd option enables OpenMP* SIMD compilation. It is set by default now. In order to disable it please use /Qopenmp-simd- option explicitly.
/GS option tells the compiler to generate code that detects some buffer overruns. This option has been added for Microsoft* compatibility. Implementation of option /GS became more extensive (for example, more routines are protected) in 18.0 compiler version. Starting from 19.0 version canary bytes are cleared right after read with /GS option specified to mitigate possible attack through stack read after exception.
Visual Studio 2019 Projects workflow and menus have changed from previous Visual Studio versions. Please read this article for information on how to create new Fortran projects under Visual Studio 2019.
Now it is possible to use Intel Fortran Compiler in compilervars environment within VS2017 Build Tools without installation of entire Microsoft* Visual Studio 2017 IDE.
Currently Intel Fortran projects (.vfproj) do not support MSBuild so they cannot be built within VS2017 Build Tools. To build them please install one of supported VS versions or VS2015 Shell.
Context-sensitive help accessed through the F1 key is restored in Intel® Parallel Studio XE 2019. Please download the compiler documentation and install it as described here. To access the documentation online follow the links from the Getting Started Guide, which can be viewed from the help menu.
The online help format is now browser-based. When you view Intel documentation from the Microsoft Visual Studio Help menu, or when you view context-sensitive help using F1 or a help button in a dialog box or other GUI element, your default browser shows the corresponding help topic. You may encounter some minor functionality issues depending on your default browser. Known issues include:
Projects using Coarray Fortran features for 32bit configurations, builds, and runs are deprecated and will be removed in the release following 19.0. Change your Project Configuration to x64 for a 64bit build and environment where Coarrays are fully supported.
/Qrcd option deprecated
The Loop Profiler feature is deprecated in the 19.0 compiler and will be removed in future compiler release. The following compiler options related to Loop Profiler are deprecated and will be removed in future compiler release:
/Qprofile-loops:keyword, /Qprofile-loops-report=value, /Qprofile-functions, /Qguide-profile
Microsoft* has announced the stand-alone Microsoft Visual Studio Shell* will not be available for Visual Studio 2017. As such, we are no longer providing a standalone shell. An integrated shell is available as part of the full Microsoft Visual Studio bundle. Please refer to https://visualstudio.microsoft.com/vs/ for further information on the Microsoft Visual Studio product offerings.
Please refer to the Intel Developer Zone article for more details.
Rogue Wave* IMSL* Fortran Numerical Library is no longer available directly from Intel. It can be obtained directly from Rogue Wave* or Rogue Wave* resellers.
Microsoft Windows 8.x* is not supported with Intel® Parallel Studio XE 2019.
Support for installation on IA-32 hosts was removed in Intel® Parallel Studio XE 2018.
The Intel® Xeon Phi™ x100 product family coprocessor (formerly code name Knights Corner) was officially announced end of life in January 2017. As part of the end of life process, the support for this family will only be available in the Intel® Parallel Studio XE 2017 version. Intel® Parallel Studio XE 2017 will be supported for a period of 3 years ending in January 2020 for the Intel® Xeon Phi™ x100 product family. Support will be provided for those customers with active support.
The filename in compiler diagnostics for filenames containing Japanese characters may be displayed incorrectly when compiled within a Windows command shell using the native Intel® 64 architecture compiler. It is not a problem when using Visual Studio or when using the Intel® 64 architecture cross-compiler.
To enable debugging Fortran code called from a .NET managed code application in Visual Studio 2012 or later, unset the following configuration:
Menu Tools ->Options, under section Debugging->General, clear the Managed C++ Compatibility Mode check box
For any managed code application, one must also check the project property Debug > Enable unmanaged code debugging.
The use of PARAMETER constants along with the /debug-parameter and /debug options may cause an internal compiler error.
The following example demonstrates usage that triggers an internal error:
module sample_mod implicit none integer, parameter :: isize=32 contains subroutine example1 call example2(isize) end subroutine example1 subroutine example2(jsize) integer, intent(in) :: jsize write(*,*) jsize end subroutine example2 end module sample_mod
It is possible to experience several internal errors during a build attempt for the Debug configuration under Visual Studio where it is common to have /debug-parameter and /debug options enabled simultaneously.
You can work-around the defect by either:
When using Microsoft Visual Studio Express*, compilation for IA-32 with -debug (General > Debug Information Format) enabled may result the warning:
warning #31001: The dll for reading and writing the pdb (for example, mspdb110.dll) could not be found on your path. This is usually a configuration error. Compilation will continue using /Z7 instead of /Zi, but expect a similar error when you link your program.
The warning is expected and occurs because a 64 bit Windows* applications (i.e. the Intel® Fortran compiler) must use 64 bit dlls (https://msdn.microsoft.com/en-us/library/windows/desktop/aa384231(v=vs.85).aspx); however, Microsoft Visual Studio Express* only provides a 32 bit version of mspdb*.dll. The missing 64 bit version leads to the warning. This is a warning-level diagnostic that does not impede successfully building an executable; however, debug information requested is embedded into the object (.obj) file for use with the debugger. No .pdb file is produced by the compiler when /Z7 is enabled.
The OpenMP* 4.5 rules states that if a threadprivate directive specifying a common block name appears in one program unit, then such a directive must also appear in every other program unit that contains a COMMON statement specifying the same name. It must appear after the last such COMMON statement in the program unit. The Intel Fortran compiler does not properly diagnose this.
For example, the following program does not conform to the OpenMP* 4.5 specification and ifort does not diagnose and issue an error for the COMMON statements following the OMP THREADPRIVATE statement according to the rule above.
Coarray Fortran 32-bit doesn't work on Microsoft* Windows 10 or Microsoft* Windows Server 2012 R2 (only on 64-bit OS) due to required utilities “mpiexec.exe” and “smpd.exe” not working properly. It is a compatibility issue. Please refer to
Coarray Fortran 32-bit doesn't work on 64-bit Microsoft* Windows for more details.
The error "Invalid command line argument: vs2019" can occur when starting a command line environment from the Start menu shortcuts, or when invoking compilervars.bat from a Command Window. See this article for additional information
Microsoft Visual Studio 2010* brought several changes that primarily affect building of mixed-language applications where the main program is in C or C++. These changes were carried forward into Visual Studio 2013/2015/2017.
If you will be building Intel® 64 (x64) configurations:
Click on the Solution Explorer tab, or press Ctrl-Alt-L, to make it visible again.
If you do not see the Microsoft.Cpp.x64.user property page listed for the x64 configuration, right click on Debug|x64 and select Add Existing property Sheet. Browse to the location which contains the MsBuild 4.0 property pages.
On Windows 7 and Windows 10, it is typically:
You may need to enable viewing of hidden files and folders to see these paths.
Select Microsoft.Cpp.x64.user.props and click Open. Now follow the steps above.
If you are converting a project from an earlier version of Visual Studio and had established Project Dependencies, these are converted to References by Visual Studio 2013/2015/2017. A Fortran project that is referenced by a C/C++ project will prevent the C/C++ project from building, with an MSB4075 error. To solve this:
Now you have to reestablish project dependencies.
Unlike earlier versions of Visual Studio, Visual Studio 2012 does not automatically link in the output library of dependent projects, so you will need to add those libraries explicitly to the parent project under Linker > Additional Dependencies. You can use the Visual Studio macros $(ConfigurationName) and $(PlatformName) as required to qualify the path. For example:
Where $(ConfigurationName) will expand to Release or Debug, as appropriate. Similarly, $(PlatformName) will expand to Win32 or x64 as appropriate.
When no browser is registered as the handler for .htm* files, viewing documentation under the IDE via Help > Intel Compilers and Libraries can result in an error popup indicating "No apps are installed to open this type of link (file)".
To resolve this issue, select the preferred browser for the file type .htm under either Control Panel > View by: large (or small) icons > Default programs > Associate a file type or protocol with a program / Set your default programs -or- Settings > System > Default Apps > Choose Default Apps by File type.
There are different integration issues observed with Microsoft* Visual Studio 2017. Problems are intermittent and not reproducible on every system. Please refer to Intel® Software Development Tools Integration to Microsoft* Visual Studio 2017 Issues for details.
Context menu item Intel Compiler > Guided Auto Parallelism > Run Analysis on Routine… is unavailable for the routine selected in the editor starting from Microsoft* Visual Studio 2017 (version 15.4). You can still run analysis on range of lines, file or project. The issue is planned to be fixed in a future release.
User can encounter the issue with freezing of Visual Studio 2017 during opening projects from file explorer when Intel compiler integration is installed. The workaround is to open project from VS. The fix is already implemented and will be available in the next update.
User can encounter the issue with empty class view of Fortran Project. The workaround is to manually delete all existing intermediate files (.fdz and others) and ensure that following setting are enabled in Tools ->Options -> Text Editor -> Fortran ->Advanced:
When debugging a Fortran program Microsoft* Visual Studio 2017 version 15.7.x or version 15.8.x crashes. In addition there is another issue that Fortran array values are not visible at a breakpoint. Please find this article for more details.
This error affects re-integration into Microsoft* Visual Studio 2019 ONLY. The Uninstall function for Intel Fortran for Windows Integrations into Visual Studio 2019 does not completely uninstall the Integrations into Visual Studio 2019. Some components are left installed. This can cause an error if you uninstall Intel Fortran for Windows version 2019 Update 4 and then try to re-install 2019 Update 4 or later – the subsequent installation into Visual Studio 2019 will fail with an error message and leave you unable to re-install the compiler into Visual Studio 2019. This error does not affect other versions of Visual Studio, only Visual Studio 2019 and observed with Intel® Parallel Studio XE 2019 Update 4 Composer Edition only.
Please refer to the article for more details.
The Intel® Fortran Compiler now supports all features from the Fortran 2008 standard. The Intel® Fortran Compiler also supports features from the proposed draft Fortran 2018 standard. Additional features will be supported in future releases. Features from the proposed Fortran 2018 standard supported by the current version include:
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL(R) PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. Go to:
The Intel® Fortran Compiler is provided under Intel’s End User License Agreement (EULA).
Please consult the licenses included in the distribution for details.
Intel, the Intel logo, the Intel Inside logo, Xeon, and Intel Xeon Phi are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.
* Other names and brands may be claimed as the property of others.
Copyright © 2018 Intel Corporation. All Rights Reserved.
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserverd for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804