I saw the same failures on both power 8 and power 9. runcpu -c wds_test.cfg --rebuild -n 1 -v 9 527.cam4_r . . . Running 527.cam4_r refrate (ref) base none (1 copy) [2019-05-24 09:26:33] /home/seurer/gcc/cpu2017/bin/specinvoke -d /home/seurer/gcc/cpu2017/benchspec/CPU/527.cam4_r/run/run_base_refrate_none.0000 -f speccmds.cmd -q -e speccmds.err -o speccmds.stdout 527.cam4_r: copy 0 non-zero return code (exit code=0, signal=11) **************************************** Contents of cam4_r_base.none.err **************************************** Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x7fffb7f804a7 in ??? #1 0x7fffb7a3369c in ??? #2 0x106364cb in ??? #3 0x1006bbaf in ??? #4 0x1006bc47 in ??? #5 0x1020a98f in ??? #6 0x1044e807 in ??? #7 0x1046a4d3 in ??? #8 0x104b725f in ??? #9 0x10003517 in ??? #10 0x7fffb79a391f in ??? #11 0x7fffb79a3b1b in ??? #12 0xffffffffffffffff in ??? similary for 521.wrf_r Running 521.wrf_r refrate (ref) base none (1 copy) [2019-05-24 10:25:28] /home/seurer/gcc/cpu2017/bin/specinvoke -d /home/seurer/gcc/cpu2017/benchspec/CPU/521.wrf_r/run/run_base_refrate_none.0000 -f speccmds.cmd -q -e speccmds.err -o speccmds.stdout 521.wrf_r: copy 0 non-zero return code (exit code=0, signal=11) **************************************** Contents of wrf.err **************************************** Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x3fffac0804d7 in ??? #1 0x11077c48 in ??? #2 0x11090c2f in ??? #3 0x110924d7 in ??? #4 0x110a524f in ??? #5 0x10c61113 in ??? #6 0x11340fef in ??? #7 0x113838a7 in ??? #8 0x10d449bf in ??? #9 0x11240fb3 in ??? #10 0x10004473 in ??? #11 0x3fffabaf309b in ???
I will work on trying to extract a smaller test case. 527.cam4_r may be the better one to look at as it runs only about 10% as long (clock wise) as the other before failing.
I think there's a duplicate and some Fortran rev. was identified as the cause.
Yes, it's dup of PR90539. Thomas now has a test-case and he's working on a patch. *** This bug has been marked as a duplicate of bug 90539 ***