- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This code snippet:
#include <exception> #include <iostream> int main() { try { throw std::runtime_error("Hello World!"); } catch (const std::exception &e) { std::cout << e.what() << std::endl; } return 0; }
Produces the following output:
1>------ Rebuild All started: Project: HelloWorld, Configuration: Debug Win32 ------ 1>stdafx.cpp 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\include\xmemory0(189): error : identifier "__STDCPP_DEFAULT_NEW_ALIGNMENT__" is undefined 1> enable_if_t<(!_HAS_ALIGNED_NEW || _Align <= __STDCPP_DEFAULT_NEW_ALIGNMENT__), int> = 0> inline 1> ^ 1> 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\include\xtr1common(59): error : class "std::enable_if<<error-constant>, int>" has no member "type" 1> using enable_if_t = typename enable_if<_Test, _Ty>::type; 1> ^ 1> detected during instantiation of type "std::enable_if_t<<error-constant>, int>" at line 189 of "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\include\xmemory0" 1> 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\include\xmemory0(208): error : identifier "__STDCPP_DEFAULT_NEW_ALIGNMENT__" is undefined 1> enable_if_t<(!_HAS_ALIGNED_NEW || _Align <= __STDCPP_DEFAULT_NEW_ALIGNMENT__), int> = 0> inline 1> ^ 1> 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\include\memory(2514): error : access violation 1> enable_if_t<is_array_v<_Ty> && extent_v<_Ty> == 0, int> = 0> 1> ^ 1> 1>compilation aborted for stdafx.cpp (code 4) 1>Done building project "HelloWorld.vcxproj" -- FAILED. ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
- Tags:
- CC++
- Development Tools
- Intel® C++ Compiler
- Intel® Parallel Studio XE
- Intel® System Studio
- Optimization
- Parallel Computing
- Vectorization
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi~this problem can be solved by reinstalling Parallel Studio XE 2018 Update2 instead of Parallel Studio XE 2017 Update*.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Did you mean VS2017 15.7.1? If so, you hit this issue because Intel compiler (version 17.0) doesn't support VS2017 15.7.1. It only supports up to VS2017 15.3.*.
Thanks,
Viet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Viet Hoang (Intel) wrote:
Did you mean VS2017 15.7.1? If so, you hit this issue because Intel compiler (version 17.0) doesn't support VS2017 15.7.1. It only supports up to VS2017 15.3.*.
Thanks. I will test 2018 (update 2) with 15.7.1. Do you know if ICC 17 will be updated to support > VS2017 15.3.* or has that version of ICC gone EOL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good results with 15.7.x and ICC 18 Update 2. I would still be interested to know if ICC 17 will see another update or if 15.3.x is the terminal stop for that product.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can anyone from Intel comment as to whether or not support for VS 15.7.x is on the update roadmap for ICC 17?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page