Strange segmentation faults of 3 SPEC_CPU_2017 fprate benchmarks

[Dongyuan_Z_]

Hi guys,

I compiled and statically linked binaries from the SPEC CPU 2017 benchmark suite. But there are three fprate benchmarks always giving strange segmentation faults. They are '503.bwaves_r', '521.wrf_r' and '527.cam4_r', and the following is the 503.bwaves_r error message. Could anyone shed light on the root cause of the issue and how it can be resolved?

The ICC version is 17.0.4. The flags that I used for compilation and linking are as follows: 

• LDCFLAGS        = -static -mkl -static-intel
• SSE            = -xCORE-AVX2
• OPTIMIZE       = $(SSE) -static -ipo -O3 -no-prec-div -qopt-prefetch -auto-p32 -ansi-alias

Thanks a bunch!

Don

ubuntu@1p2650v4-9:/bmark/xeon-1p2650v4-specrate-spec/0/benchspec/CPU/503.bwaves_r/run/run_base_refrate_x86_64_icc_mkl-m64.0023$ ../run_base_refrate_x86_64_icc_mkl-m64.0000/bwaves_r_base.x86_64_icc_mkl-m64 bwaves_1 < bwaves_1.in

 BI-CGSTAB & symmetric difference scheme
 3D  Laminar shock wave propagation
 Re:   100000.000000    Pr:        0.720000
 grid size is:     63    63    64
 CFL:  2.000   nuim:  0.100  nuex2:  0.100 nuex4:  0.050
 Implicit scheme is working
 Cubic initial configuration
 Number of Time Steps:     80

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
bwaves_r_base.x86  0000000000417B74  Unknown               Unknown  Unknown
bwaves_r_base.x86  00000000004AE6B0  Unknown               Unknown  Unknown
bwaves_r_base.x86  00000000004024F8  Unknown               Unknown  Unknown
bwaves_r_base.x86  0000000000401DE6  Unknown               Unknown  Unknown
bwaves_r_base.x86  000000000040112E  Unknown               Unknown  Unknown
bwaves_r_base.x86  00000000004AD034  Unknown               Unknown  Unknown
bwaves_r_base.x86  00000000004AD166  Unknown               Unknown  Unknown
bwaves_r_base.x86  0000000000401016  Unknown               Unknown  Unknown

[Viet_H_Intel]

Can you rebuild with an additional -g flag, so that if SIGSEGV occurs, it would give you more info.

Regards,

Viet Hoang