Compiler fails with: internal error: assertion failed at: "shared/cfe/edgcpfe/scope_stk.c"

[Vasko_Mitanov]

Using beast library and example from https://github.com/vinniefalco/Beast/tree/master.

Using ICC: 17.0.1 20161005

When compiling the example, compiler fails with "internal error":

In file included from /home/vasko/xxx/ext/beast/include/beast/core/handler_concepts.hpp(11),

                 from /home/vasko/xxx/ext/beast/include/beast/core/async_completion.hpp(11),
                 from /home/vasko/xxx/ext/beast/include/beast/http/parse.hpp(12),
                 from /home/vasko/xxx/ext/beast/include/beast/http.hpp(17),
                 from /home/vasko/xxx/yyy/request_handler.hpp(6),
                 from /home/vasko/xxx/yyy/server.hpp(1),
                 from /home/vasko/xxx/yyy/main.cpp(1):
/home/vasko/xxx/ext/beast/include/beast/core/detail/is_call_possible.hpp(41): internal error: assertion failed at: "shared/cfe/edgcpfe/scope_stk.c", line 11203

      : decltype(is_call_possible_test<R>(
                 ^

Any clue?

Vasko

[Vasko_Mitanov]

Same code compiles and runs without any problem on Linux using GCC and Windows using MSVC 2015

[Yuan_C_Intel]

Hi, Vasko

Thank you for reporting this issue.

Could you generate a preprocessed(*.i) file for main.cpp, which can help reproduce the crash?

You can use compiler option -P instead of -c, change -o object file name to *.i to generate the preprocessed file.

You may refer to below article on how to create a preprocessed file:

https://software.intel.com/en-us/articles/how-to-create-a-preprocessed-file-i-file

Thanks.

[Vasko_Mitanov]

Hi Yolanda,

Please find the attached inlined sample code.

Please be aware that there is a padding with hundreds of empty lines at the begin of the file.

Thanks,

Vasko

[Yuan_C_Intel]

Hi, Vask

Thank you for providing the preprocessed file.

I can reproduce your issue now with icc 17.0. I have recorded this in our problem tracking system. 

We will try to resolve this issue as soon as we can. However, please be advised that this issue may have to be targeted to for the next major release. I will let you know when I have an update on this issue.

Thank you.

[Yuan_C_Intel]

Hi, Vask

This is a known issue and we have fixed in engineering stage. The fix should be available in our next release 17.0 Update 2.

Thanks.