- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am using "Intel Parallel Studio XE 2016 Update 2". I get the following error when I try to compile my program using "Intel C++ 16.0" compiler
demcem_ws_st_rwg.cpp(44) (col. 18): : error : assertion failed at: "shared/cfe/edgglue/edg_decl.c", line 1468
Where line (44) in demcem_ws_st_rwg.cpp is
complex<double> Isub[3][3][3];
If I switch to "Visual C++ 2015" compiler I get no error and the program compiles successfully. Both build are x64.
The simple test case below also does not work
#include <complex> using namespace std; int main() { complex<double> Isub[3][3][3]; return 0; }
How can I resolve this problem?
Thanks!
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't see any such problem with your reproducer, running with icl 16.0.2 and VS2015.1+windows kits 10.0.10240.0. I might suspect a mismatch among Microsoft include folders. My VS2015 installation broke several times with Microsoft automatic upgrades, until the update 1 with the menu selection for SDK 10240 came along. The Windows version may be relevant if you're trying to avoid using 10240. For example, it may be possible to get by with the combination of windows kits 8.1 and 10.0.10150.
I'm a little surprised if you don't see the same problem with ICL and the same version of VC which ICL is using.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Tim. I can't reproduce it either.
I'm using Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23506 for x64, with Windows 10 sdk 10.0.10240.0
and
Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 16.0.2.180 Build 20160204
I did a straight compile like this: icl -c -EHsc test.cpp
Am I missing some options?
--Melanie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the replies.
I repaired Visual Studio 2015 and it worked! So I guess it had to do with the Microsoft automatic updates!
Thanks again

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page