Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Luke_D_
Beginner
2,937 Views

icpc: error #10106: Fatal error

Jump to solution

Encountered on the devcloud...

icpc: error #10106: Fatal error in /glob/development-tools/versions/intel-parallel-studio/compilers_and_libraries_2019.3.199/linux/bin/intel64/mcpcom, terminated by kill signal

Command argmuments

-Wall -Wextra  -wd1011 -O3   -qopenmp -std=gnu++17 

Attached preprocessed source.

0 Kudos
1 Solution
Viet_H_Intel
Moderator
2,937 Views

It compiled OK for me.

$ icpc -Wall -Wextra  -wd1011 -O3   -qopenmp -std=gnu++17 -c Filters.cpp -o Filters.o

$ icpc -V
Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 19.0.3.199 Build 20190206
Copyright (C) 1985-2019 Intel Corporation.  All rights reserved.

$ ls -lt Filters.o
-rw-r--r-- 1 vahoang ome 299832 Dec 13 11:48 Filters.o
 

View solution in original post

8 Replies
Luke_D_
Beginner
2,937 Views

Preprocessed source.

Viet_H_Intel
Moderator
2,937 Views

What compiler version is it? 

I can't untar the tar ball.

$ ls -lt Filters.cpp.bz2 
-rw-r--r-- 1 vahoang ome 204825 Dec 13 09:11 Filters.cpp.bz2
$ tar -xvjf Filters.cpp.bz2 
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
$

Luke_D_
Beginner
2,937 Views

It's not a tarball... it's just a bzip-ed preprocessed source. Try bunzip?

 

******@login-1:~/cswarm/mrwt/build$ icpc --version
icpc (ICC) 19.0.3.199 20190206
Copyright (C) 1985-2019 Intel Corporation.  All rights reserved.

 

Luke_D_
Beginner
2,937 Views
******@login-1:~/temp$ bunzip2 Filters.cpp.bz2 
******@login-1:~/temp$ icpc -Wall -Wextra  -wd1011 -O3   -qopenmp -std=gnu++17 -c Filters.cpp -o Filters.o
icpc: error #10106: Fatal error in /glob/development-tools/versions/intel-parallel-studio/compilers_and_libraries_2019.3.199/linux/bin/intel64/mcpcom, terminated by kill signal
compilation aborted for Filters.cpp (code 1)
******@login-1:~/temp$

It runs for a long time... maybe it's just running OOM? It's not giving me any information about what kind of signal I'm getting...

Viet_H_Intel
Moderator
2,938 Views

It compiled OK for me.

$ icpc -Wall -Wextra  -wd1011 -O3   -qopenmp -std=gnu++17 -c Filters.cpp -o Filters.o

$ icpc -V
Intel(R) C++ Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 19.0.3.199 Build 20190206
Copyright (C) 1985-2019 Intel Corporation.  All rights reserved.

$ ls -lt Filters.o
-rw-r--r-- 1 vahoang ome 299832 Dec 13 11:48 Filters.o
 

View solution in original post

Luke_D_
Beginner
2,937 Views

Okay. I guess that it's system specific to intel's devcloud environment... maybe something ulimit based. I'll try and figure out who to contact about that. Thanks

Viet_H_Intel
Moderator
2,937 Views

Ok, it took about 2mins to compile, btw

Luke_D_
Beginner
2,937 Views

Viet Hoang (Intel) wrote:

Ok, it took about 2mins to compile, btw

Yeah, that's consistent with what I see. We've always had very long compiles (and ICE) with our use of "modern" C++ and icc. Generally I use clang and gcc during development cycles and then go back to icc at the end of a cycle for performance analysis. I'm looking forward to the Next version to see if icc can play a more direct role during development. I can compile on one of the compute nodes that has a newer icc and different ulimits, so I can compile Filter... now I'm just getting a normal ICE elsewhere from EDG.

Reply