Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
37 Views

internal error: assertion failed at: "shared/cfe/edgcpfe/exprutil.c"

I've experienced issues with compiling a code that I cannot disclose here but I managed to remove unrelated parts and this small part of code seems to cause internal error: assertion failed at: "shared/cfe/edgcpfe/exprutil.c", line 19869 when I compiled it with ICL at the line of std::cout

#include <iostream>
#include <iomanip>
#include <fstream>
#include <stdexcept>
#include <cmath>
#include <string>
#include <sstream>

#define to_stringSP3( x ) static_cast< std::ostringstream & >( ( std::ostringstream() << std::fixed << std::setprecision(3)<< std::dec << x ) ).str()

int main(){
	float f;
	std::cin >> f;
	std::cout << to_stringSP3(f) << "\n";
}

 

My colleagues informed me that this piece of code does not give any error at older versions of ICL

My version

ICL

Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 18.0.6.287 Build 20190527
Copyright (C) 1985-2019 Intel Corporation.  All rights reserved.

 

CL

Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27031.1 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

 

 

 

 

 

 

0 Kudos
2 Replies
Highlighted
Moderator
37 Views

Seems like you are using Microsoft VS 2019, which is not supported by this ICL 18.0 version. Can you try with IPSXE2019 update 4?

0 Kudos
Highlighted
Beginner
37 Views

Hello Viet, thanks for returning, I have Visual Studio 2019, 2017, 2008 etc installed. For build system we use msys, in order to setup environment variables I call script from Parallel Studio 

call "C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2018.6.287\windows\bin\ipsxe-comp-vars.bat" intel64 vs2017

so I was expecting it to use compiler from vs2017. My company has commercial licence for vs2017 so I should use it if possible.

0 Kudos