Intel® C++ Compiler
Support and discussions for creating C++ code that runs on platforms based on Intel® processors.
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
7569 Discussions

Internal error loop: assertion failed: find_seq_in_lookup_table: seq_number not found (shared/cfe/edgcpfe/il.c, line 4039)

Jakob__Wenzel
Beginner
369 Views

Hi,

I'm running into a pesky internal compiler error with the attached preprocessed file. It would be great if this could be fixed.

$ icpc test.ii -std=c++14 -xMIC-AVX512
Internal error loop: assertion failed: find_seq_in_lookup_table: seq_number not found (shared/cfe/edgcpfe/il.c, line 4039)

Thanks,
Wenzel

0 Kudos
7 Replies
Jakob__Wenzel
Beginner
369 Views

This is the compiler version: 

icpc version 16.0.3 (gcc version 4.9.3 compatibility)
ld    /usr/lib/../lib64/crt1.o /usr/lib/../lib64/crti.o /ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/crtbegin.o --eh-frame-hdr --build-id -dynamic-linker /lib64/ld-linux-x86-64.so.2 -m elf_x86_64 -o a.out -L/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/bin/lib_lin -L/ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/ -L/ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/../../../../lib64 -L/ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/../../../../lib64/ -L/lib/../lib64 -L/lib/../lib64/ -L/usr/lib/../lib64 -L/usr/lib/../lib64/ -L/ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/../../../ -L/lib64 -L/lib/ -L/usr/lib64 -L/usr/lib -L/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/ipp/lib/intel64 -rpath=/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/ipp/lib/intel64 -L/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/tbb/lib/intel64/gcc4.4 -rpath=/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/tbb/lib/intel64/gcc4.4 -L/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/mkl/lib/intel64 -rpath=/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/mkl/lib/intel64 -L/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/compiler/lib/intel64 -rpath=/ssoft/spack/external/intel/2016/compilers_and_libraries_2016.3.210/linux/compiler/lib/intel64 -rpath=/ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64 -Bdynamic -Bstatic -limf -lsvml -lirng -Bdynamic -lstdc++ -lm -Bstatic -lipgo -ldecimal --as-needed -Bdynamic -lcilkrts --no-as-needed -lstdc++ -lgcc -lgcc_s -Bstatic -lirc -lsvml -Bdynamic -lc -lgcc -lgcc_s -Bstatic -lirc_s -Bdynamic -ldl -lc /ssoft/spack/lafnetscha/opt/spack/x86_E5v1_IntelIB/gcc-4.4.7/gcc-4.9.3-2gys3tu6lq35ge6woeixfo4tfz5nnvzn/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/crtend.o /usr/lib/../lib64/crtn.o

Judith_W_Intel
Employee
369 Views

 

Thanks for reporting this. I have reduced it to this small example below which gives the assertion even in our development compiler.

I have entered  DPD200413420 in our internal tracking bugs database to fix this bug. thanks for reporting it.

As you can see it looks to be a problem that is triggered by inheriting constructors.

template <typename Type>
void foo2(Type x) {
    Type(double(1));
}

struct B2
{
    B2(double);
};

struct B : public B2 {
    using B2::B2;
    B();
};

struct A : public B
{
    using B::B;
};

void foo() {
  A a;
  foo2(a);
}

lukas_m_
Beginner
369 Views
Hi all, thanks for reporting this issue and this small example. We are struggling with the same internal compiler error in our codes, but we were not able to recognize where the problem is. We are using icpc (ICC) 17.0.0 20160721 and the bug still holds. Internal error loop: assertion failed: find_seq_in_lookup_table: seq_number not found (shared/cfe/edgcpfe/il.c, line 4094) Will this bug be fixed for next release? Do you have any workaround at the moment? Thanks, Lukas.
Judith_W_Intel
Employee
369 Views

 

This was fixed in 17.0 on 09/26 so yes it should be fixed in 17.0 update 1 which should be available very soon.

Sorry but I can't think of a simple workaround

Judy

Viet_H_Intel
Moderator
369 Views

Hi Lukas,

We've released 17.0 Update 1 which has this problem fixed.

$ icc -V
Intel(R) C Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 17.0.1.132 Build 20161005

Thanks,

Viet

 

Chawla__Kashp
Beginner
369 Views

Is this issue also resolved in icc16, if yes which version? 

Viet_H_Intel
Moderator
369 Views

We don't have any more update for icc16.

Reply