- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, everyone,
For Boost.Python builds using ICC on Windows got error:
libs\python\src\object\enum.cpp(47): internal error: assertion failed: remove_from_routines_list: routine not found on list (shared/cfe/edgcpfe/il.c, line 16415) object auto_free(handle<>(mod)); ^ compilation aborted for libs\python\src\object\enum.cpp (code 4)
(original 'enum.cpp' and its ICC-preprocessed version added in attachment).
Reproduced for:
- Boost 1.66.0.b1.rc2 builds using ICC,
not reproduced for:
- Boost 1.65.1 builds using ICC,
- Boost 1.66.0.b1.rc2 builds using mingw-w64 and MSVC.
Environment:
- Windows 10 x64,
- ICC 2018 Update 1,
- MSVC 2017 15.4.1,
- Windows SDK 10.0.16299.15,
- mingw-w64 x86_64 7.2.0,
- Boost 1.66.0.b1.rc2.
Best,
Alexander
- Tags:
- CC++
- Development Tools
- Intel® C++ Compiler
- Intel® Parallel Studio XE
- Intel® System Studio
- Optimization
- Parallel Computing
- Vectorization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for reporting this. I have reduced it to the following code (which only fails on Windows):
namespace boost {
extern "C"
void foo()
{
void auto_free(int);
}
}
It seems to be a problem with a block scope declaration inside an extern "C" routine which is inside a namespace.
I have submitted this in our internal compilers database as cmplrs-47253.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for reporting this. I have reduced it to the following code (which only fails on Windows):
namespace boost {
extern "C"
void foo()
{
void auto_free(int);
}
}
It seems to be a problem with a block scope declaration inside an extern "C" routine which is inside a namespace.
I have submitted this in our internal compilers database as cmplrs-47253.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After moving to IPSXE 2018 Update 2 error not reproduced. Thank you for fix!
Best,
Alexander

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