Intel® C++ Compiler for Windows* 19.1 Release Notes for Parallel Studio XE 2020
This document provides a summary of new and changed product features and includes notes about features and problems not described in the product documentation.
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® C++ Compiler 19.1.
- Change History
- System Requirements
- How to Use
- Documentation
- Intel-provided debug solutions
- Samples
- Technical Support
- New and Changed Features in 19.1
- Parallel STL for parallel and vector execution of the C++ STL
- Support Deprecated
- Support Removed
- Known Limitations
- Disclaimer and Legal Information
Change History
Changes in Update 4 (Intel® C++ Compiler 19.1.3)
- The Intel® Compilers contain functional and security updates.
- The Intel® C++ Compiler includes intrinsics for Intel® Advanced Matrix Extensions (Intel® AMX).
Changes in Update 3
- Not applicable for Windows*.
Note: Intel® Parallel Studio XE 2020 Update 3 is available for the Intel® Parallel Studio XE 2020 Composer Edition for C++ Linux*.
This is a Linux-only release: there is no Update 3 release for either Windows* or macOS* operating systems.
In addition, it is only a Composer Edition release: there is no Update 3 release for either Professional or Cluster Editions of Intel® Parallel Studio XE 2020.
There is no update to the Intel® C++ Compilers Redistributable Libraries. The Update 2 versions of these libraries are compatible and should be used.
There is no update for the Intel® Parallel Studio XE Runtime 2020 YUM* and APT* repository packages. Continue to use the Update 2 packages of this runtime.
Changes in Update 2 (New in Intel® C++ Compiler 19.1.2)
- Corrections to reported problems.
Changes in Update 1 (New in Intel® C++ Compiler 19.1.1)
- Corrections to reported problems.
Changes since Intel® C++ Compiler 19.0 (New in Intel® C++ Compiler 19.1)
- This release contains support for Integrations into Visual Studio 2019
- New compiler option /Qbranches-within-32B-boundaries[-]
- New C++20 features supported
- New features from OpenMP 5.0*
- Access to Intel® C++ Compiler next generation code generator
System Requirements
- 2GB of RAM (4GB recommended)
- 4GB free disk space for all features
- Microsoft Windows 10*, or Microsoft Windows Server 2019* , Microsoft Windows Server 2016* [1]
- Development of "Windows 8 Modern UI" applications is not supported. [2]
- To use the Microsoft Visual Studio development environment or command-line tools to build IA-32 or Intel® 64 architecture applications, one of:
- Microsoft Visual Studio 2017* Professional Edition with 'Desktop development with C++' component installed
- Microsoft Visual Studio 2019* Professional Edition with 'Desktop development with C++' component installed
- To use command-line tools only to build Intel® 64 architecture applications, one of:
- Microsoft Windows* Software Development Kit for Windows 10*
Notes
- Applications can be run on the same Windows versions as specified above for development. Applications may also run on non-embedded 32-bit versions of Microsoft Windows earlier than Windows XP, though Intel does not test these for compatibility. Your application may depend on a Win32 API routine not present in older versions of Windows. You are responsible for testing application compatibility. You may need to copy certain run-time DLLs onto the target system to run your application.
- The Intel® C++ Compiler does not support development of Windows 8* UI apps. We are always interested in your comments and suggestions. For example, if you want to use the Intel® C++ Compiler or other Intel software development capabilities in Windows 8 UI apps, please file a request at Intel® Online Service Center (http://www.intel.com/supporttickets).
- To use the Intel® C++ Compiler with Microsoft Visual Studio 2017*, it is necessary to install the 'Desktop developement with C++ component from Visual Studio. This article explains how.
- This article explains how to use the Intel® C++ Compiler with Microsoft Visual Studio 2017*,
How to use the Intel® C++ Compiler
Intel® Parallel studio XE 2020: Getting started with the Intel® C++ Compiler for Windows* at <install-dir>\documentation_2020\en\compiler_c\ps2020\get_started_wc.htm. contains information on how to use the Intel® C++ Compiler from the command line and from Microsoft Visual Studio*.
Documentation
Product documentation is linked from <install-dir>\documentation_2020\en\compiler_c\ps2020\get_started_wc.htm.
Online Help format in Microsoft Visual Studio*
New help menu items to link to online getting started documents.
Context sensitive help on F1 is not available
Offline Core Documentation Removed from the Installed Image
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 can also download an offline version of the documentation from the Intel® Software Development Products Registration Center: Product List > Intel® Parallel Studio XE Documentation.
Please use the instructions from this article to add Intel® Compiler documentation to your local machine.
Japanese Language Support
Japanese language support is provided with this version of the product.
Intel-provided debug solutions
- Intel®-provided debug solutions are based GNU* GDB. Please see Intel® Parallel Studio XE 2020 Composer Edition C++ - Debug Solutions Release Notes for further information.
Samples
Product samples are now available online at Intel® Software Product Samples and Tutorials
Technical Support
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: /content/www/us/en/developer/get-help/overview.html
Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.
New and Changed Features
The following features are new or significantly enhanced in this version. For more information on these features, please refer to the documentation.
New compiler option /Qbranches-within-32B-boundaries[-]
This option is supported in versions 19.0 update 8 of the compiler and above. The details about this option can be found in the Intel® C++ Compiler 19.1 Developer Guide and Reference here.
To find more information, see https://www.intel.com/content/dam/support/us/en/documents/processors/mitigations-jump-conditional-code-erratum.pdf
Access Intel® C++ Compiler next generation code generator
/Qnextgen compiler option invokes the Intel® C++ Compiler next generation code generator. These options are only available for Windows* or Linux* ICC/ICL/ICPC drivers. This option and functionality is not available for Intel® C++ Compiler for macOS* X.
The Intel® C++ Compiler 19.1 supports the following features under the /Qstd=c++20 (Windows*) or -std=c++20 (Linux*/OS X*) options:
- std::is_constant_evaluated and __builtin_is_constant_evaluated
- IF clause on SIMD directive
- NONTEMPORAL clause on SIMD directive
Parallel STL for parallel and vector execution of the C++ STL
Intel(R) C++ Compiler is installed with Parallel STL, an implementation of the C++ standard library algorithms with support for execution policies.
Features/API changes
- More algorithms support parallel and vector execution policies: find_first_of, is_heap, is_heap_until, replace, replace_if.
- More algorithms support vector execution policies: remove, remove_if.
- More algorithms support parallel execution policies: partial_sort.
To learn more, please refer to article https://software.intel.com/en-us/get-started-with-pstl
Support Deprecated
none at this time
Support Removed
Intel® Cilk™ Plus support is removed in 19.1.
This includes the "#pragma simd" directive. Users should replace with the OpenMP SIMD pragma "#pragma omp simd" and it's clauses. Remember to add compiler option "/Qopenmp-simd" or "/Qopenmp". This pragma will be removed in a future release.
Microsoft Visual Studio 2013* and Microsoft Visual Studio 2015* support removed
Microsoft Visual Studio 2013* and Microsoft Visual Studio 2015* are not supported with Intel® Compiler 19.1.
Microsoft Windows 7*, Windows Server 2008 R2 SP1*, Windows Server 2012* are not supported
Microsoft Windows 7*, Windows Server 2008 R2 SP1*, Windows Server 2012* are not supported with Intel® C++ Compiler 19.1.
The Loop Profiler feature will be removed in future compilers.
The following compiler options related to Loop Profiler are deprecated and will be removed in future compilers
- /Qprofile-loops=keyword
- /Qprofile-loops-report=value
- /Qprofile-functions
- /Qguide-profile
Known Limitations
Visual Studio 2019 16.8 preview breaks ICL for <utility> AND /std:c++latest
Please refrain from upgrading Visual Studio until this issue is fixed. Please refer here for more details.
Warning message when running psxevars.bat from Command Prompt.
When running the psxevars.bat script from the Command Prompt to set The compiler environment you will get a warning or error message. This message can be ignored – your environment will work properly after running psxevars.bat. Just ignore the warning messages about “The system cannot find the file specified.”
Ignore it and continue to use the Command Prompt.
Parallel STL
unseq and par_unseq policies only have effect with compilers that support '#pragma omp simd' or '#pragma simd. Parallel and vector execution is only supported for a subset of algorithms if random access iterators are provided, while for the rest execution will remain serial. Depending on a compiler, zip_iterator may not work with unseq and par_unseq policies.
Pointer Checker requires a dynamic runtime library
When using the /Qcheck-pointers option, the runtime library libchkp.dll must be linked in. When using options like /MD with /Qcheck-pointers, be aware that this dynamic library will be linked in regardless of your settings. See the article at http://intel.ly/1jV0eWD for more information.
Intel® Compiler Help Documentation fails to launch from IDE when installed on Japanese version of Windows*
Some multi-pane documents do not display correctly in the Visual Studio* internal browser
There is a limitation of Visual Studio* internal browser that some multi-pane documents do not display correctly, the table of contents appears in the left pane, but the right pane does not display any content.
Workaround: Access the same documentation from the Visual Studio Help menu.
- User can encounter the issue with freezing of VS2017 during opening projects from file explorer when Intel compiler integration is installed. The workaround is to open project from VS.
- In mixed ICL/MSVC compilation projects you can face the following problem in VS2017 U4 or older:
“The "ConformanceMode" parameter is not supported by the "CL" task. Verify the parameter exists on the task, and it is a settable public instance property.”
The workaround is to update VS2017 or comment the following line inside two sections in\Common7\IDE\VC\VCTargets\Platforms\ \PlatformToolsets\Intel C++ Compiler 19.0\Toolset.targets file: “ConformanceMode ="%(ClCompile.ConformanceMode)"”
- MSVCP90D.dll (or other Microsoft runtime DLL) is missing
There are situations where the sample projects provided (or any Microsoft Visual C++* project potentially) could run into a runtime System Error where the application cannot find a Microsoft Visual Studio* runtime DLL. This is related to manifest files and SXS assemblies potentially missing. The simplest solution is to go to your redist directory for the version of Microsoft Visual Studio* you are using (default location would be c:\program files[ (x86)]\Microsoft Visual Studio X.X\VC\redist). There will be several subdirectories under this location, sorting files out by amd64, x86 or Debug_NonRedist (if you have D in the runtime name, this usually indicates a Debug library found in this folder). Find the appropriate folder that contains the runtime you are looking for, and then copy the entire contents of that folder (including a .manifest file) to the directory where the .exe you are trying to run is located.
Viewing Intel Compiler Documentation in Microsoft Edge* browser on Japanese Windows 10 OS
-
There is an issue when viewing the Intel Compiler Documentation in Microsoft Edge* browser on Japanese Windows 10 OS. The upper left corner [Content][Index][Search] buttons does not work. When clicking on it, it results in blank screen.
-
This issue is being investigated. Please use Internet Explorer to view the Intel Compiler Documentation. To set the default browser to Internet Explorer, google search "how to make Internet Explorer default browser on Windows 10".
Disclaimer and Legal Information
Optimization Notice |
---|
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:
http://www.intel.com/products/processor%5Fnumber/
The Intel® C++ Compiler is provided under Intel's End User License Agreement (EULA).
Please consult the licenses included in the distribution for details.
Intel, Intel logo, Pentium, Core, Atom, Iris, Intel® Xeon®, Intel® Xeon Phi™, and Cilk are trademarks of Intel Corporation in the U.S. and other countries.
* Other names and brands may be claimed as the property of others.
Copyright © 2019 Intel Corporation. All Rights Reserved.