To run SPEC2017 test suite, you should build spec tools first.
specmake is one of those tools built. But it is executed with errors, so we can not use it.
Now we create symlink "specmake" on native make to workaround this problem.
Also, we change sha512sum for specmake in TOOLS.sha512 file to pass an integrity check.
You can see the output log of specmake error below or in the file:
make_error.log
runcpu v5825
Using 'linux-arc-HSDKv1' tools
Reading file manifests... read 32282 entries from 2 files in 1.96s (16449 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 53 benchsets.
Reading config file '/home/root/build/config/arc.cfg'
1 configuration selected:
Action Run Mode Workload Report Type Benchmarks
-------- -------- -------- ---------------- ---------------------------
validate rate refrate SPECrate2017_int 500.perlbench_r
-------------------------------------------------------------------------------
Setting up environment for running 500.perlbench_r...
Starting runcpu for 500.perlbench_r...
Running "specperl /home/root/build/bin/sysinfo" to gather system information.
sysinfo: r5974 of 2018-05-19 (9bcde8f2999c33d61f64985e45859ea9)
sysinfo: Getting system information for Linux...
sysinfo: ...getting CPU info
sysinfo: ...getting info from numactl
sysinfo: ...getting memory info
sysinfo: ...getting OS info
sysinfo: ...getting disk info
Retrieving flags file (/home/root/build/config/flags/gcc.xml)...
Benchmarks selected: 500.perlbench_r
Compiling Binaries
Building 500.perlbench_r base mytest-m32: (build_base_mytest-m32.0000) [2020-04-08 15:25:53]
potentially unexpected fatal signal 11.
Path: /home/root/build/bin/specmake
CPU: 0 PID: 524 Comm: specmake Not tainted 5.3.15 #1
[ECR ]: 0x00040000 => Insn could not be fetched
[EFA ]: 0x00000000
[BLINK ]: 0x200b8660
[ERET ]: 0x0
@No matching VMA found
[STAT32]: 0x80080082 : IE U
BTA: 0x00000000 SP: 0x5fe936f4 FP: 0x5fe93890
LPS: 0x20098c00 LPE: 0x20098c08 LPC: 0x00000000
r00: 0x5fe936f4 r01: 0x5fe93720 r02: 0x00000000
r03: 0x00055756 r04: 0x00000000 r05: 0x00000000
r06: 0x2013a5c4 r07: 0x00000020 r08: 0x00048008
r09: 0x00000000 r10: 0x20010a80 r11: 0x2001c980
r12: 0x200b8660 r13: 0x2012747c r14: 0x5fe936f4
r15: 0x5fe93d64 r16: 0x00000118 r17: 0x00055748
r18: 0x0000000e r19: 0x00000001 r20: 0x00000001
r21: 0x0000000d r22: 0x00000204 r23: 0x5fe938c8
r24: 0x00000000 r25: 0x2013e47c
Error with make.clean 'specmake --output-sync --jobs=1 clean'; no non-empty output files exist
Command exited with signal 11
*** Error building 500.perlbench_r base
Build successes for intrate: None
Build errors for intrate: 500.perlbench_r(base; CE)
NOTICE: Nothing to run! No results will be generated.
The log for this run is in /home/root/build/result/CPU2017.003.log
runcpu finished at 2020-04-08 15:25:57; 24 total seconds elapsed
To run SPEC2017 test suite, you should build spec tools first. specmake is one of those tools built. But it is executed with errors, so we can not use it. Now we create symlink "specmake" on native make to workaround this problem. Also, we change sha512sum for specmake in TOOLS.sha512 file to pass an integrity check.
You can see the output log of specmake error below or in the file: make_error.log