Intel® C++ Compiler 19.1 for Windows* Release Notes for Intel® oneAPI Beta

By Varsha Madananth,

Published:07/15/2019   Last Updated:07/15/2019

Overview

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

New in Intel® C++ Compiler 19.1 Technology Preview

Back to top

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

  1. 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.
  2. 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).
  3. 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 to use the Intel® C++ Compiler with Microsoft Visual Studio 2017*.

Back to top

How to use the Intel® C++ Compiler

Refer to Get started with Intel® oneAPI High Performance Computing Toolkit

Please see Getting Started Guide for Intel C/C++ Compiler with OpenMP offload.

Back to top

Documentation

 Full documentation for all tool components is available at the oneAPI page.

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

Back to top

Samples

Product samples are now available online at Intel® Software Product Samples and Tutorials

Back to top

Technical Support

Any issues found should be reported to the oneAPI tools for internal Jira project

For details on issue submission including requesting access to the Jira project, please see Guidelines on Reporting Issues

For general discussions on oneAPI usage, please submit questions to the discussion forum on Inside Blue.

Back to top

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.

Early Access Intel® C++ Compiler Based on the Modern LLVM* Framework, aka ICC NextGen

/Qnextgen compiler option invokes the Early Access ICC NextGen compiler. These options are only available for Windows* or Linux* ICC/ICL/ICPC drivers. This option and functionality is not available for ICC on macOS* X.

C++20 features supported

The Intel® C++ Compiler 19.1 Technology Preview 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

Features from OpenMP 5.0*

  • IF clause on SIMD directive
  • NONTEMPORAL clause on SIMD directive

Back to top

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

Support Removed

Intel® Cilk™ Plus support is removed in 19.1

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

 

Back to top

Known Limitations

-D__INTEL_COMPILER=1901

The predefined macro __INTEL_COMPILER is set to 1901. The compiler version is 19.1. We are looking to change this predefine to 1910 in a future updates and in the 19.1 product release.

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.

Visual Studio Known Issues

  • 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".

Back to top

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 © 2018 Intel Corporation. All Rights Reserved.

Back to top

 

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.

Give Feedback