SPEC CPU 2017 Ubuntu 20.04 LTS cpu2017-1_0_5.iso 安装、测试 单核成绩 笔记

news/2024/11/7 21:01:32/

环境

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.4.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) 
$ lscpu
架构:                           x86_64
CPU 运行模式:                   32-bit, 64-bit
字节序:                         Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU:                             6
在线 CPU 列表:                  0-5
每个核的线程数:                 1
每个座的核数:                   6
座:                             1
NUMA 节点:                      1
厂商 ID:                        GenuineIntel
CPU 系列:                       6
型号:                           158
型号名称:                       Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
步进:                           13
CPU MHz:                        800.010
CPU 最大 MHz:                   4600.0000
CPU 最小 MHz:                   800.0000
BogoMIPS:                       7399.70
虚拟化:                         VT-x
L1d 缓存:                       192 KiB
L1i 缓存:                       192 KiB
L2 缓存:                        1.5 MiB
L3 缓存:                        9 MiB
NUMA 节点0 CPU:                 0-5
Vulnerability Itlb multihit:     KVM: Mitigation: Split huge pages
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Mitigation; Clear CPU buffers; SMT disabled
Vulnerability Retbleed:          Mitigation; Enhanced IBRS
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:             Mitigation; Microcode
Vulnerability Tsx async abort:   Mitigation; TSX disabled
标记:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities

依赖

sudo apt install gfortran

安装SPEC CPU 2017

sudo mkdir /mnt/cpu2017
sudo mount cpu2017-1_0_5.iso /mnt/cpu2017/
cd /mnt/cpu2017/
bash install.sh -d /home/speccpu/cpu2017

安装日志

SPEC CPU2017 InstallationTop of the CPU2017 tree is '/mnt/cpu2017'Installing FROM /mnt/cpu2017
Installing TO /home/speccpu/cpu2017Is this correct? (Please enter 'yes' or 'no') 
yesThe following toolset is expected to work on your platform.  If the
automatically installed one does not work, please re-run install.sh and
exclude that toolset using the '-e' switch.The toolset selected will not affect your benchmark scores.linux-x86_64                  For x86_64 Linux systemsBuilt on Oracle Linux 6.0 withGCC v4.4.4 20100726 (Red Hat 4.4.4-13)=================================================================
Attempting to install the linux-x86_64 toolset...Unpacking CPU2017 base files (44 MB)
Unpacking CPU2017 tools binary files (150.2 MB)
Unpacking 500.perlbench_r benchmark and data files (102 MB)
Unpacking 502.gcc_r benchmark and data files (240.3 MB)
Unpacking 503.bwaves_r benchmark and data files (0.2 MB)
Unpacking 505.mcf_r benchmark and data files (8.5 MB)
Unpacking 507.cactuBSSN_r benchmark and data files (12.5 MB)
Unpacking 508.namd_r benchmark and data files (8.3 MB)
Unpacking 510.parest_r benchmark and data files (25.6 MB)
Unpacking 511.povray_r benchmark and data files (23.3 MB)
Unpacking 519.lbm_r benchmark and data files (4.3 MB)
Unpacking 520.omnetpp_r benchmark and data files (56.6 MB)
Unpacking 521.wrf_r benchmark and data files (217.2 MB)
Unpacking 523.xalancbmk_r benchmark and data files (212 MB)
Unpacking 525.x264_r benchmark and data files (57.9 MB)
Unpacking 526.blender_r benchmark and data files (215.7 MB)
Unpacking 527.cam4_r benchmark and data files (348.6 MB)
Unpacking 531.deepsjeng_r benchmark and data files (0.5 MB)
Unpacking 538.imagick_r benchmark and data files (80.7 MB)
Unpacking 541.leela_r benchmark and data files (3.8 MB)
Unpacking 544.nab_r benchmark and data files (38.6 MB)
Unpacking 548.exchange2_r benchmark and data files (0.1 MB)
Unpacking 549.fotonik3d_r benchmark and data files (5.2 MB)
Unpacking 554.roms_r benchmark and data files (11.4 MB)
Unpacking 557.xz_r benchmark and data files (104.1 MB)
Unpacking 600.perlbench_s benchmark and data files (3.1 MB)
Unpacking 602.gcc_s benchmark and data files (0.9 MB)
Unpacking 603.bwaves_s benchmark and data files (0 MB)
Unpacking 605.mcf_s benchmark and data files (0.1 MB)
Unpacking 607.cactuBSSN_s benchmark and data files (0.1 MB)
Unpacking 619.lbm_s benchmark and data files (30.4 MB)
Unpacking 620.omnetpp_s benchmark and data files (0.1 MB)
Unpacking 621.wrf_s benchmark and data files (0.3 MB)
Unpacking 623.xalancbmk_s benchmark and data files (0.1 MB)
Unpacking 625.x264_s benchmark and data files (0.2 MB)
Unpacking 627.cam4_s benchmark and data files (0.5 MB)
Unpacking 628.pop2_s benchmark and data files (283.8 MB)
Unpacking 631.deepsjeng_s benchmark and data files (0.2 MB)
Unpacking 638.imagick_s benchmark and data files (0.3 MB)
Unpacking 641.leela_s benchmark and data files (0 MB)
Unpacking 644.nab_s benchmark and data files (0.1 MB)
Unpacking 648.exchange2_s benchmark and data files (0 MB)
Unpacking 649.fotonik3d_s benchmark and data files (0.1 MB)
Unpacking 654.roms_s benchmark and data files (1.1 MB)
Unpacking 657.xz_s benchmark and data files (0.2 MB)
Unpacking 996.specrand_fs benchmark and data files (0 MB)
Unpacking 997.specrand_fr benchmark and data files (0 MB)
Unpacking 998.specrand_is benchmark and data files (0 MB)
Unpacking 999.specrand_ir benchmark and data files (6.4 MB)Checking the integrity of your source tree...Checksums are all okay.Unpacking binary tools for linux-x86_64...Checking the integrity of your binary tools...Checksums are all okay.Testing the tools installation (this may take a minute)...................................................................................................................................................................................................................................................................................................................-.......Installation successful.  Source the shrc or cshrc in
/home/speccpu/cpu2017
to set up your environment for the benchmark.

配置

gcc.cfg

cd /home/speccpu/cpu2017/config/
cp Example-gcc-linux-x86.cfg gcc.cfg

配置gcc路径

*** Example-gcc-linux-x86.cfg	2021-12-16 19:24:09.000000000 +0800
--- gcc.cfg	2023-07-05 11:49:55.369840502 +0800
*************** default:
*** 151,157 ****#      WARNING: See section "Older GCC" above.#%ifndef %{gcc_dir}
! %   define  gcc_dir        "/opt/rh/devtoolset-9/root/usr"  # EDIT (see above)%endif# EDIT: If your compiler version is 10 or greater, you must enable the next 
--- 151,157 ----#      WARNING: See section "Older GCC" above.#%ifndef %{gcc_dir}
! %   define  gcc_dir        "/usr"  # EDIT (see above)%endif# EDIT: If your compiler version is 10 or greater, you must enable the next 
*************** default:               # data model appl
*** 254,280 ****511.povray_r=peak:                       # https://www.spec.org/cpu2017/Docs/benchmarks/511.povray_r.htmlEXTRA_CFLAGS = -fno-strict-aliasing 521.wrf_r,621.wrf_s=peak:                # https://www.spec.org/cpu2017/Docs/benchmarks/521.wrf_r.html
! %     ifdef %{GCCge10}                      # workaround for GCC v10 (and presumably later)
!          EXTRA_FFLAGS = -fallow-argument-mismatch
! %     endif527.cam4_r,627.cam4_s=peak:              # https://www.spec.org/cpu2017/Docs/benchmarks/527.cam4_r.htmlEXTRA_CFLAGS = -fno-strict-aliasing 
! %     ifdef %{GCCge10}                      # workaround for GCC v10 (and presumably later)
!          EXTRA_FFLAGS = -fallow-argument-mismatch
! %     endif# See also topic "628.pop2_s basepeak" below628.pop2_s=peak:                         # https://www.spec.org/cpu2017/Docs/benchmarks/628.pop2_s.html
! %     ifdef %{GCCge10}                      # workaround for GCC v10 (and presumably later)
!          EXTRA_FFLAGS = -fallow-argument-mismatch
! %     endif## FP workarounds - base - combine the above - https://www.spec.org/cpu2017/Docs/runrules.html#BaseFlags#fprate,fpspeed=base:    EXTRA_CFLAGS = -fno-strict-aliasing 
! %     ifdef %{GCCge10}                      # workaround for GCC v10 (and presumably later)
!          EXTRA_FFLAGS = -fallow-argument-mismatch
! %     endif#-------- Tuning Flags common to Base and Peak --------------------------------
--- 254,275 ----511.povray_r=peak:                       # https://www.spec.org/cpu2017/Docs/benchmarks/511.povray_r.htmlEXTRA_CFLAGS = -fno-strict-aliasing 521.wrf_r,621.wrf_s=peak:                # https://www.spec.org/cpu2017/Docs/benchmarks/521.wrf_r.html
!       EXTRA_FFLAGS = -fallow-argument-mismatch527.cam4_r,627.cam4_s=peak:              # https://www.spec.org/cpu2017/Docs/benchmarks/527.cam4_r.htmlEXTRA_CFLAGS = -fno-strict-aliasing 
!       EXTRA_FFLAGS = -fallow-argument-mismatch
! # See also topic "628.pop2_s basepeak" below628.pop2_s=peak:                         # https://www.spec.org/cpu2017/Docs/benchmarks/628.pop2_s.html
!       EXTRA_FFLAGS = -fallow-argument-mismatch
! ## FP workarounds - base - combine the above - https://www.spec.org/cpu2017/Docs/runrules.html#BaseFlags#fprate,fpspeed=base:    EXTRA_CFLAGS = -fno-strict-aliasing 
!       EXTRA_FFLAGS = -fallow-argument-mismatch
! 

gcc.xml

直接使用config/flags/gcc.xml

在线更新 SPEC CPU 2017

source shrc
runcpu --update

日志

(base) yeqiang@yeqiang-MS-7B23:/home/speccpu/cpu2017$ runcpu --update
SPEC CPU(r) 2017 Benchmark Suites
Copyright 1995-2017 Standard Performance Evaluation Corporation (SPEC)runcpu v5825
Using 'linux-x86_64' tools
Reading file manifests... read 32272 entries from 2 files in 0.08s (402042 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 53 benchsets.CPU2017 update mode selected
Downloading update information...Selected update:From v1.0.5 to v1.1.9Update size: 35 MBDownloading update metadata: 6745 B (18 KB/s)
Update metadata parsed successfully.Update summary:Files to remove: 21Directories to remove: 0Files to change: 584Files to add: 101
Update metadata downloaded and verified.Checking files that will be changed or removed by the update...
Checks completed.
Update: Downloading update: 35 MB/35 MB (100%; 1982 KB/s))
Update downloaded and verified.Uncompressing update fileProceed with update? (y/n)
ySuite update successful!There is no log file for this run.runcpu finished at 2023-07-03 14:55:49; 80 total seconds elapsed

测试

单核整形、浮点

cd /home/speccpu/cpu2017
source shrc
runcpu -c gcc.cfg -T base -s -F config/flags/gcc.xml -n 3 -C 0 -i ref intrate fprate

日志

yeqiang@yeqiang-MS-7B23:/home/speccpu/cpu2017$ runcpu -c gcc.cfg -T base -s -F config/flags/gcc.xml -n 3 -C 0 -i ref intrate fprate
SPEC CPU(r) 2017 Benchmark Suites
Copyright 1995-2019 Standard Performance Evaluation Corporation (SPEC)runcpu v6612
Using 'linux-x86_64' tools
Reading file manifests... read 32225 entries from 2 files in 0.12s (261611 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 73 benchsets.
Reading config file '/home/speccpu/cpu2017/config/gcc.cfg'
2 configurations selected:Action    Run Mode   Workload     Report Type      Benchmarks
--------   --------   --------   ----------------   ---------------------------
validate   rate       refrate    SPECrate2017_int   intrate                    
validate   rate       refrate    SPECrate2017_fp    fprate                     
Downloading update information for version check...
OKVersion 1.1.9 of CPU2017 is the latest available.Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
-------------------------------------------------------------------------------Setting up environment for running intrate...
Starting runcpu for intrate...
Running "specperl /home/speccpu/cpu2017/bin/sysinfo" to gather system information.
sysinfo: r6732 of 2022-11-07 (fe91c89b7ed5c36ae2c92cc097bec197)
sysinfo: ...getting basic information about kernel, users, and limits
sysinfo: Getting system information for Linux...
sysinfo: ...getting CPU info
sysinfo: ...getting info from numactl
sysinfo: ...getting memory info
sysinfo: ...getting info from systemd
sysinfo: ...getting power info
sysinfo: ...getting system tuning info
sysinfo: ...getting OS info
sysinfo: ...getting disk info
sysinfo: ...getting info from /sys/devices/virtual/dmi/id
sysinfo: ...getting info from dmidecode
Retrieving flags file (config/flags/gcc.xml)...
Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
Benchmarks selected: 500.perlbench_r, 502.gcc_r, 505.mcf_r, 520.omnetpp_r, 523.xalancbmk_r, 525.x264_r, 531.deepsjeng_r, 541.leela_r, 548.exchange2_r, 557.xz_r, 999.specrand_ir
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesUp to date 500.perlbench_r base mytest-m64Up to date 502.gcc_r base mytest-m64Up to date 505.mcf_r base mytest-m64Up to date 520.omnetpp_r base mytest-m64Up to date 523.xalancbmk_r base mytest-m64Up to date 525.x264_r base mytest-m64Up to date 531.deepsjeng_r base mytest-m64Up to date 541.leela_r base mytest-m64Up to date 548.exchange2_r base mytest-m64Up to date 557.xz_r base mytest-m64Up to date 999.specrand_ir base mytest-m64Setting Up Run DirectoriesSetting up 500.perlbench_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 502.gcc_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 505.mcf_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 520.omnetpp_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 523.xalancbmk_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 525.x264_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 531.deepsjeng_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 541.leela_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 548.exchange2_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 557.xz_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 999.specrand_ir test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000
Running BenchmarksRunning 500.perlbench_r test base mytest-m64 (1 copy) [2023-07-05 08:29:29]Running 502.gcc_r test base mytest-m64 (1 copy) [2023-07-05 08:29:53]Running 505.mcf_r test base mytest-m64 (1 copy) [2023-07-05 08:29:53]Running 520.omnetpp_r test base mytest-m64 (1 copy) [2023-07-05 08:30:02]Running 523.xalancbmk_r test base mytest-m64 (1 copy) [2023-07-05 08:30:08]Running 525.x264_r test base mytest-m64 (1 copy) [2023-07-05 08:30:09]Running 531.deepsjeng_r test base mytest-m64 (1 copy) [2023-07-05 08:30:28]Running 541.leela_r test base mytest-m64 (1 copy) [2023-07-05 08:30:34]Running 548.exchange2_r test base mytest-m64 (1 copy) [2023-07-05 08:30:38]Running 557.xz_r test base mytest-m64 (1 copy) [2023-07-05 08:30:46]Running 999.specrand_ir test base mytest-m64 (1 copy) [2023-07-05 08:30:56]
Success: 1x500.perlbench_r 1x502.gcc_r 1x505.mcf_r 1x520.omnetpp_r 1x523.xalancbmk_r 1x525.x264_r 1x531.deepsjeng_r 1x541.leela_r 1x548.exchange2_r 1x557.xz_r 1x999.specrand_ir
Benchmarks selected: 500.perlbench_r, 502.gcc_r, 505.mcf_r, 520.omnetpp_r, 523.xalancbmk_r, 525.x264_r, 531.deepsjeng_r, 541.leela_r, 548.exchange2_r, 557.xz_r, 999.specrand_ir
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesUp to date 500.perlbench_r base mytest-m64Up to date 502.gcc_r base mytest-m64Up to date 505.mcf_r base mytest-m64Up to date 520.omnetpp_r base mytest-m64Up to date 523.xalancbmk_r base mytest-m64Up to date 525.x264_r base mytest-m64Up to date 531.deepsjeng_r base mytest-m64Up to date 541.leela_r base mytest-m64Up to date 548.exchange2_r base mytest-m64Up to date 557.xz_r base mytest-m64Up to date 999.specrand_ir base mytest-m64Setting Up Run DirectoriesSetting up 500.perlbench_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 502.gcc_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 505.mcf_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 520.omnetpp_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 523.xalancbmk_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 525.x264_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 531.deepsjeng_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 541.leela_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 548.exchange2_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 557.xz_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 999.specrand_ir train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000
Running BenchmarksRunning 500.perlbench_r train base mytest-m64 (1 copy) [2023-07-05 08:31:40]Running 502.gcc_r train base mytest-m64 (1 copy) [2023-07-05 08:31:59]Running 505.mcf_r train base mytest-m64 (1 copy) [2023-07-05 08:32:32]Running 520.omnetpp_r train base mytest-m64 (1 copy) [2023-07-05 08:33:17]Running 523.xalancbmk_r train base mytest-m64 (1 copy) [2023-07-05 08:34:02]Running 525.x264_r train base mytest-m64 (1 copy) [2023-07-05 08:34:31]Running 531.deepsjeng_r train base mytest-m64 (1 copy) [2023-07-05 08:34:46]Running 541.leela_r train base mytest-m64 (1 copy) [2023-07-05 08:35:28]Running 548.exchange2_r train base mytest-m64 (1 copy) [2023-07-05 08:36:31]Running 557.xz_r train base mytest-m64 (1 copy) [2023-07-05 08:36:54]Running 999.specrand_ir train base mytest-m64 (1 copy) [2023-07-05 08:37:21]
Success: 1x500.perlbench_r 1x502.gcc_r 1x505.mcf_r 1x520.omnetpp_r 1x523.xalancbmk_r 1x525.x264_r 1x531.deepsjeng_r 1x541.leela_r 1x548.exchange2_r 1x557.xz_r 1x999.specrand_ir
Benchmarks selected: 500.perlbench_r, 502.gcc_r, 505.mcf_r, 520.omnetpp_r, 523.xalancbmk_r, 525.x264_r, 531.deepsjeng_r, 541.leela_r, 548.exchange2_r, 557.xz_r, 999.specrand_ir
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesUp to date 500.perlbench_r base mytest-m64Up to date 502.gcc_r base mytest-m64Up to date 505.mcf_r base mytest-m64Up to date 520.omnetpp_r base mytest-m64Up to date 523.xalancbmk_r base mytest-m64Up to date 525.x264_r base mytest-m64Up to date 531.deepsjeng_r base mytest-m64Up to date 541.leela_r base mytest-m64Up to date 548.exchange2_r base mytest-m64Up to date 557.xz_r base mytest-m64Up to date 999.specrand_ir base mytest-m64Setting Up Run DirectoriesSetting up 500.perlbench_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 502.gcc_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 505.mcf_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 520.omnetpp_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 523.xalancbmk_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 525.x264_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 531.deepsjeng_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 541.leela_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 548.exchange2_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 557.xz_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002Setting up 999.specrand_ir refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0002
Running BenchmarksRunning (#1) 500.perlbench_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 08:37:52]Running (#1) 502.gcc_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 08:42:09]Running (#1) 505.mcf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 08:45:20]Running (#1) 520.omnetpp_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 08:50:01]Running (#1) 523.xalancbmk_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 08:55:49]Running (#1) 525.x264_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:00:10]Running (#1) 531.deepsjeng_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:02:45]Running (#1) 541.leela_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:06:44]Running (#1) 548.exchange2_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:13:04]Running (#1) 557.xz_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:17:43]Running (#1) 999.specrand_ir refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:22:50]Running (#2) 500.perlbench_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:22:51]Running (#2) 502.gcc_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:27:11]Running (#2) 505.mcf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:30:21]Running (#2) 520.omnetpp_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:35:03]Running (#2) 523.xalancbmk_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:40:48]Running (#2) 525.x264_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:45:03]Running (#2) 531.deepsjeng_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:47:37]Running (#2) 541.leela_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:51:35]Running (#2) 548.exchange2_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 09:57:55]Running (#2) 557.xz_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:02:31]Running (#2) 999.specrand_ir refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:07:33]Running (#3) 500.perlbench_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:07:34]Running (#3) 502.gcc_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:11:51]Running (#3) 505.mcf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:15:00]Running (#3) 520.omnetpp_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:19:41]Running (#3) 523.xalancbmk_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:25:31]Running (#3) 525.x264_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:29:56]Running (#3) 531.deepsjeng_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:32:34]Running (#3) 541.leela_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:36:49]Running (#3) 548.exchange2_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:43:28]Running (#3) 557.xz_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:48:13]Running (#3) 999.specrand_ir refrate (ref) base mytest-m64 (1 copy) [2023-07-05 10:53:39]
Success: 3x500.perlbench_r 3x502.gcc_r 3x505.mcf_r 3x520.omnetpp_r 3x523.xalancbmk_r 3x525.x264_r 3x531.deepsjeng_r 3x541.leela_r 3x548.exchange2_r 3x557.xz_r 3x999.specrand_ir
Producing Raw Reportslabel: mytest-m64workload: refrate (ref)metric: SPECrate2017_int_baseformat: raw -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.rsf
Parsing flags for 500.perlbench_r base: done
Parsing flags for 502.gcc_r base: done
Parsing flags for 505.mcf_r base: done
Parsing flags for 520.omnetpp_r base: done
Parsing flags for 523.xalancbmk_r base: done
Parsing flags for 525.x264_r base: done
Parsing flags for 531.deepsjeng_r base: done
Parsing flags for 541.leela_r base: done
Parsing flags for 548.exchange2_r base: done
Parsing flags for 557.xz_r base: done
Doing flag reduction: doneformat: flags -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.flags.htmlformat: cfg -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.cfg, /home/speccpu/cpu2017/result/CPU2017.007.intrate.orig.cfgformat: CSV -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.csvformat: PDF -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.pdfformat: HTML -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.htmlformat: Text -> /home/speccpu/cpu2017/result/CPU2017.007.intrate.txtformat: Reportable Check -> FAILED.  Found the following errors:- The fw_bios field must include this phrase:"Version <id> released MMM-YYYY"where: "Version" (or "version") is literal text."<id>" is the version identifier string as seen by customers.The <id> may include multiple words and/or punctuation."released" (or "Released") is literal text."MMM" is the three-letter English month abbreviation."YYYY" is the full four digit year.No value for fw_bios was specified.- The "hw_avail" field is invalid.It must be MMM-YYYY, where YYYY is the full four digityear, and MMM is the three-letter English month abbreviation.- The "hw_cpu_max_mhz" field is invalid.It must be entirely numeric.The current value is "".- The "hw_cpu_nominal_mhz" field is invalid.It must be entirely numeric.The current value is "".- Fractional memory size in the "hw_memory000" field."31.275 GB" should be changed to "32025 MB"- The hw_model field must not be empty.- The "hw_ncores" field is invalid.It must be entirely numeric.The current value is "".- The "hw_ncpuorder" field is invalid.The value must contain a number, list ofnumbers, or range of numbers, followed by a unit.The current value is "".- The "hw_nthreadspercore" field is invalid.It must be entirely numeric.The current value is "".- The other cache description (hw_ocache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_ocache was specified.- The "hw_other" field is invalid.The value must be non-blank.  If you are not usingany other hardware relevant to SPEC CPU performance,you can say "None" here.- The primary cache description (hw_pcache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <chip|core>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <chip|core>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, TB,or "<prefix> micro-ops", and [] indicates optional content.No value for hw_pcache was specified.- The secondary cache description (hw_scache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_scache was specified.- The tertiary cache description (hw_tcache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_tcache was specified.- The "license_num" field is invalid.It must be numeric, with or without a leading or trailing "A".The current value is "nnn (Your SPEC license number)".- The "notes_*.*?_*" field (any field matching "notes_*.*?_*\d+") is missing.- The "power_management" field is invalid.This field is used to briefly summarize any non-default settings forpower management, whether set in BIOS, firmware, operating system, orelsewhere.Details of the settings are in the power notes section of the result.- The "sw_avail" field is invalid.It must be MMM-YYYY, where YYYY is the full four digityear, and MMM is the three-letter English month abbreviation.- The "sw_other" field is invalid.The value must be non-blank and may not begin with "--".If you are not using any other software relevant to SPECCPU performance, you must say "None" here.-------------------------------------------------------------------------------Setting up environment for running fprate...
Starting runcpu for fprate...
Running "specperl /home/speccpu/cpu2017/bin/sysinfo" to gather system information.
sysinfo: r6732 of 2022-11-07 (fe91c89b7ed5c36ae2c92cc097bec197)
sysinfo: ...getting basic information about kernel, users, and limits
sysinfo: Getting system information for Linux...
sysinfo: ...getting CPU info
sysinfo: ...getting info from numactl
sysinfo: ...getting memory info
sysinfo: ...getting info from systemd
sysinfo: ...getting power info
sysinfo: ...getting system tuning info
sysinfo: ...getting OS info
sysinfo: ...getting disk info
sysinfo: ...getting info from /sys/devices/virtual/dmi/id
sysinfo: ...getting info from dmidecode
Retrieving flags file (config/flags/gcc.xml)...
Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
Benchmarks selected: 503.bwaves_r, 507.cactuBSSN_r, 508.namd_r, 510.parest_r, 511.povray_r, 519.lbm_r, 521.wrf_r, 526.blender_r, 527.cam4_r, 538.imagick_r, 544.nab_r, 549.fotonik3d_r, 554.roms_r, 997.specrand_fr
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesBuilding 503.bwaves_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:53:50]Building 507.cactuBSSN_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:53:52]Building 508.namd_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:54:25]Building 510.parest_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:54:36]Building 511.povray_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:56:19]Building 519.lbm_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:56:27]Building 521.wrf_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:56:29]
Error with make.diffwrf_521 'specmake --output-sync --jobs=8 build TARGET=diffwrf_521':----------------------------------------------------------------------------Please review this file:"/home/speccpu/cpu2017/benchspec/CPU/521.wrf_r/build/build_base_mytest-m64.0000/make.diffwrf_521.out"----------------------------------------------------------------------------Command returned exit code 2Error with make!
*** Error building 521.wrf_r base
The log for this run is in /home/speccpu/cpu2017/result/CPU2017.007.log
The debug log for this run is in /home/speccpu/cpu2017/result/CPU2017.007.log.debug
*
* Temporary files were NOT deleted; keeping temporaries such as
* /home/speccpu/cpu2017/result/CPU2017.007.log.debug and
* /home/speccpu/cpu2017/tmp/CPU2017.007
* (These may be large!)
*
runcpu finished at 2023-07-05 10:56:39; 8858 total seconds elapsed

等待。。。

中途浮点编译报错了,参考前面的patch已修复。记录单独跑浮点日志

runcpu -c gcc.cfg -T base -s -F config/flags/gcc.xml -n 3 -C 0 -i ref fprate
SPEC CPU(r) 2017 Benchmark Suites
Copyright 1995-2019 Standard Performance Evaluation Corporation (SPEC)runcpu v6612
Using 'linux-x86_64' tools
Reading file manifests... read 32225 entries from 2 files in 0.08s (419089 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 73 benchsets.
Reading config file '/home/speccpu/cpu2017/config/gcc.cfg'
1 configuration selected:Action    Run Mode   Workload     Report Type     Benchmarks
--------   --------   --------   ---------------   ----------------------------
validate   rate       refrate    SPECrate2017_fp   fprate                      
Downloading update information for version check...
OKVersion 1.1.9 of CPU2017 is the latest available.Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
-------------------------------------------------------------------------------Setting up environment for running fprate...
Starting runcpu for fprate...
Running "specperl /home/speccpu/cpu2017/bin/sysinfo" to gather system information.
sysinfo: r6732 of 2022-11-07 (fe91c89b7ed5c36ae2c92cc097bec197)
sysinfo: ...getting basic information about kernel, users, and limits
sysinfo: Getting system information for Linux...
sysinfo: ...getting CPU info
sysinfo: ...getting info from numactl
sysinfo: ...getting memory info
sysinfo: ...getting info from systemd
sysinfo: ...getting power info
sysinfo: ...getting system tuning info
sysinfo: ...getting OS info
sysinfo: ...getting disk info
sysinfo: ...getting info from /sys/devices/virtual/dmi/id
sysinfo: ...getting info from dmidecode
Retrieving flags file (config/flags/gcc.xml)...
Reportable runs must include a 'test' run; adding to run list
Reportable runs must include a 'train' run; adding to run list
Benchmarks selected: 503.bwaves_r, 507.cactuBSSN_r, 508.namd_r, 510.parest_r, 511.povray_r, 519.lbm_r, 521.wrf_r, 526.blender_r, 527.cam4_r, 538.imagick_r, 544.nab_r, 549.fotonik3d_r, 554.roms_r, 997.specrand_fr
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesBuilding 503.bwaves_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:56:15]Building 507.cactuBSSN_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:56:17]Building 508.namd_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:56:47]Building 510.parest_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:56:59]Building 511.povray_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:58:35]Building 519.lbm_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:58:43]Building 521.wrf_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 11:58:44]Building 526.blender_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:09:04]Building 527.cam4_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:10:06]Building 538.imagick_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:11:03]Building 544.nab_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:11:18]Building 549.fotonik3d_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:11:21]Building 554.roms_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:11:32]Building 997.specrand_fr base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 12:11:48]Build successes for fprate: 503.bwaves_r(base), 507.cactuBSSN_r(base), 508.namd_r(base), 510.parest_r(base), 511.povray_r(base), 519.lbm_r(base), 521.wrf_r(base), 526.blender_r(base), 527.cam4_r(base), 538.imagick_r(base), 544.nab_r(base), 549.fotonik3d_r(base), 554.roms_r(base), 997.specrand_fr(base)
Build errors for fprate: NoneSetting Up Run DirectoriesSetting up 503.bwaves_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 507.cactuBSSN_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 508.namd_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 510.parest_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 511.povray_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 519.lbm_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 521.wrf_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 526.blender_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 527.cam4_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 538.imagick_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 544.nab_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 549.fotonik3d_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 554.roms_r test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000Setting up 997.specrand_fr test base mytest-m64 (1 copy): run_base_test_mytest-m64.0000
Running BenchmarksRunning 503.bwaves_r test base mytest-m64 (1 copy) [2023-07-05 12:11:56]Running 507.cactuBSSN_r test base mytest-m64 (1 copy) [2023-07-05 12:12:00]Running 508.namd_r test base mytest-m64 (1 copy) [2023-07-05 12:12:04]Running 510.parest_r test base mytest-m64 (1 copy) [2023-07-05 12:12:08]Running 511.povray_r test base mytest-m64 (1 copy) [2023-07-05 12:12:13]Running 519.lbm_r test base mytest-m64 (1 copy) [2023-07-05 12:12:13]Running 521.wrf_r test base mytest-m64 (1 copy) [2023-07-05 12:12:16]Running 526.blender_r test base mytest-m64 (1 copy) [2023-07-05 12:12:22]Running 527.cam4_r test base mytest-m64 (1 copy) [2023-07-05 12:12:23]Running 538.imagick_r test base mytest-m64 (1 copy) [2023-07-05 12:12:35]Running 544.nab_r test base mytest-m64 (1 copy) [2023-07-05 12:12:35]Running 549.fotonik3d_r test base mytest-m64 (1 copy) [2023-07-05 12:12:37]Running 554.roms_r test base mytest-m64 (1 copy) [2023-07-05 12:12:40]Running 997.specrand_fr test base mytest-m64 (1 copy) [2023-07-05 12:12:43]
Success: 1x503.bwaves_r 1x507.cactuBSSN_r 1x508.namd_r 1x510.parest_r 1x511.povray_r 1x519.lbm_r 1x521.wrf_r 1x526.blender_r 1x527.cam4_r 1x538.imagick_r 1x544.nab_r 1x549.fotonik3d_r 1x554.roms_r 1x997.specrand_fr
Benchmarks selected: 503.bwaves_r, 507.cactuBSSN_r, 508.namd_r, 510.parest_r, 511.povray_r, 519.lbm_r, 521.wrf_r, 526.blender_r, 527.cam4_r, 538.imagick_r, 544.nab_r, 549.fotonik3d_r, 554.roms_r, 997.specrand_fr
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesUp to date 503.bwaves_r base mytest-m64Up to date 507.cactuBSSN_r base mytest-m64Up to date 508.namd_r base mytest-m64Up to date 510.parest_r base mytest-m64Up to date 511.povray_r base mytest-m64Up to date 519.lbm_r base mytest-m64Up to date 521.wrf_r base mytest-m64Up to date 526.blender_r base mytest-m64Up to date 527.cam4_r base mytest-m64Up to date 538.imagick_r base mytest-m64Up to date 544.nab_r base mytest-m64Up to date 549.fotonik3d_r base mytest-m64Up to date 554.roms_r base mytest-m64Up to date 997.specrand_fr base mytest-m64Setting Up Run DirectoriesSetting up 503.bwaves_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 507.cactuBSSN_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 508.namd_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 510.parest_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 511.povray_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 519.lbm_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 521.wrf_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 526.blender_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 527.cam4_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 538.imagick_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 544.nab_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 549.fotonik3d_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 554.roms_r train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000Setting up 997.specrand_fr train base mytest-m64 (1 copy): run_base_train_mytest-m64.0000
Running BenchmarksRunning 503.bwaves_r train base mytest-m64 (1 copy) [2023-07-05 12:12:58]Running 507.cactuBSSN_r train base mytest-m64 (1 copy) [2023-07-05 12:13:21]Running 508.namd_r train base mytest-m64 (1 copy) [2023-07-05 12:13:45]Running 510.parest_r train base mytest-m64 (1 copy) [2023-07-05 12:14:04]Running 511.povray_r train base mytest-m64 (1 copy) [2023-07-05 12:14:32]Running 519.lbm_r train base mytest-m64 (1 copy) [2023-07-05 12:14:35]Running 521.wrf_r train base mytest-m64 (1 copy) [2023-07-05 12:14:52]Running 526.blender_r train base mytest-m64 (1 copy) [2023-07-05 12:15:25]Running 527.cam4_r train base mytest-m64 (1 copy) [2023-07-05 12:17:02]Running 538.imagick_r train base mytest-m64 (1 copy) [2023-07-05 12:17:16]Running 544.nab_r train base mytest-m64 (1 copy) [2023-07-05 12:17:37]Running 549.fotonik3d_r train base mytest-m64 (1 copy) [2023-07-05 12:18:37]Running 554.roms_r train base mytest-m64 (1 copy) [2023-07-05 12:18:59]Running 997.specrand_fr train base mytest-m64 (1 copy) [2023-07-05 12:20:07]
Success: 1x503.bwaves_r 1x507.cactuBSSN_r 1x508.namd_r 1x510.parest_r 1x511.povray_r 1x519.lbm_r 1x521.wrf_r 1x526.blender_r 1x527.cam4_r 1x538.imagick_r 1x544.nab_r 1x549.fotonik3d_r 1x554.roms_r 1x997.specrand_fr
Benchmarks selected: 503.bwaves_r, 507.cactuBSSN_r, 508.namd_r, 510.parest_r, 511.povray_r, 519.lbm_r, 521.wrf_r, 526.blender_r, 527.cam4_r, 538.imagick_r, 544.nab_r, 549.fotonik3d_r, 554.roms_r, 997.specrand_fr
Notice: Errors may not be ignored for reportable runs.
Compiling BinariesUp to date 503.bwaves_r base mytest-m64Up to date 507.cactuBSSN_r base mytest-m64Up to date 508.namd_r base mytest-m64Up to date 510.parest_r base mytest-m64Up to date 511.povray_r base mytest-m64Up to date 519.lbm_r base mytest-m64Up to date 521.wrf_r base mytest-m64Up to date 526.blender_r base mytest-m64Up to date 527.cam4_r base mytest-m64Up to date 538.imagick_r base mytest-m64Up to date 544.nab_r base mytest-m64Up to date 549.fotonik3d_r base mytest-m64Up to date 554.roms_r base mytest-m64Up to date 997.specrand_fr base mytest-m64Setting Up Run DirectoriesSetting up 503.bwaves_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 507.cactuBSSN_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 508.namd_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 510.parest_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 511.povray_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 519.lbm_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 521.wrf_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 526.blender_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 527.cam4_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 538.imagick_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 544.nab_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 549.fotonik3d_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 554.roms_r refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000Setting up 997.specrand_fr refrate (ref) base mytest-m64 (1 copy): run_base_refrate_mytest-m64.0000
Running BenchmarksRunning (#1) 503.bwaves_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:20:23]Running (#1) 507.cactuBSSN_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:25:45]Running (#1) 508.namd_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:28:47]Running (#1) 510.parest_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:31:25]Running (#1) 511.povray_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:37:30]Running (#1) 519.lbm_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:42:33]Running (#1) 521.wrf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:45:31]Running (#1) 526.blender_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:50:05]Running (#1) 527.cam4_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:54:12]Running (#1) 538.imagick_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 12:57:23]Running (#1) 544.nab_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:02:36]Running (#1) 549.fotonik3d_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:07:09]Running (#1) 554.roms_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:11:35]Running (#1) 997.specrand_fr refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:14:34]Running (#2) 503.bwaves_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:14:35]Running (#2) 507.cactuBSSN_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:20:03]Running (#2) 508.namd_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:23:09]Running (#2) 510.parest_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:25:52]Running (#2) 511.povray_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:33:11]Running (#2) 519.lbm_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:38:46]Running (#2) 521.wrf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:41:50]Running (#2) 526.blender_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:46:20]Running (#2) 527.cam4_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:50:31]Running (#2) 538.imagick_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:53:48]Running (#2) 544.nab_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 13:58:57]Running (#2) 549.fotonik3d_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:03:25]Running (#2) 554.roms_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:07:56]Running (#2) 997.specrand_fr refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:10:53]Running (#3) 503.bwaves_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:10:54]Running (#3) 507.cactuBSSN_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:16:22]Running (#3) 508.namd_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:19:30]Running (#3) 510.parest_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:22:15]Running (#3) 511.povray_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:28:41]Running (#3) 519.lbm_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:33:58]Running (#3) 521.wrf_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:37:04]Running (#3) 526.blender_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:41:44]Running (#3) 527.cam4_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:45:57]Running (#3) 538.imagick_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:49:14]Running (#3) 544.nab_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:54:25]Running (#3) 549.fotonik3d_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 14:58:53]Running (#3) 554.roms_r refrate (ref) base mytest-m64 (1 copy) [2023-07-05 15:03:27]Running (#3) 997.specrand_fr refrate (ref) base mytest-m64 (1 copy) [2023-07-05 15:06:26]
Success: 3x503.bwaves_r 3x507.cactuBSSN_r 3x508.namd_r 3x510.parest_r 3x511.povray_r 3x519.lbm_r 3x521.wrf_r 3x526.blender_r 3x527.cam4_r 3x538.imagick_r 3x544.nab_r 3x549.fotonik3d_r 3x554.roms_r 3x997.specrand_fr
Producing Raw Reportslabel: mytest-m64workload: refrate (ref)metric: SPECrate2017_fp_baseformat: raw -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.rsf
Parsing flags for 503.bwaves_r base: done
Parsing flags for 507.cactuBSSN_r base: done
Parsing flags for 508.namd_r base: done
Parsing flags for 510.parest_r base: done
Parsing flags for 511.povray_r base: done
Parsing flags for 519.lbm_r base: done
Parsing flags for 521.wrf_r base: done
Parsing flags for 526.blender_r base: done
Parsing flags for 527.cam4_r base: done
Parsing flags for 538.imagick_r base: done
Parsing flags for 544.nab_r base: done
Parsing flags for 549.fotonik3d_r base: done
Parsing flags for 554.roms_r base: done
Doing flag reduction: doneformat: flags -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.flags.htmlformat: cfg -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.cfg, /home/speccpu/cpu2017/result/CPU2017.009.fprate.orig.cfgformat: CSV -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.csvformat: PDF -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.pdfformat: HTML -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.htmlformat: Text -> /home/speccpu/cpu2017/result/CPU2017.009.fprate.txtformat: Reportable Check -> FAILED.  Found the following errors:- The fw_bios field must include this phrase:"Version <id> released MMM-YYYY"where: "Version" (or "version") is literal text."<id>" is the version identifier string as seen by customers.The <id> may include multiple words and/or punctuation."released" (or "Released") is literal text."MMM" is the three-letter English month abbreviation."YYYY" is the full four digit year.No value for fw_bios was specified.- The "hw_avail" field is invalid.It must be MMM-YYYY, where YYYY is the full four digityear, and MMM is the three-letter English month abbreviation.- The "hw_cpu_max_mhz" field is invalid.It must be entirely numeric.The current value is "".- The "hw_cpu_nominal_mhz" field is invalid.It must be entirely numeric.The current value is "".- Fractional memory size in the "hw_memory000" field."31.275 GB" should be changed to "32025 MB"- The hw_model field must not be empty.- The "hw_ncores" field is invalid.It must be entirely numeric.The current value is "".- The "hw_ncpuorder" field is invalid.The value must contain a number, list ofnumbers, or range of numbers, followed by a unit.The current value is "".- The "hw_nthreadspercore" field is invalid.It must be entirely numeric.The current value is "".- The other cache description (hw_ocache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_ocache was specified.- The "hw_other" field is invalid.The value must be non-blank.  If you are not usingany other hardware relevant to SPEC CPU performance,you can say "None" here.- The primary cache description (hw_pcache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <chip|core>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <chip|core>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, TB,or "<prefix> micro-ops", and [] indicates optional content.No value for hw_pcache was specified.- The secondary cache description (hw_scache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_scache was specified.- The tertiary cache description (hw_tcache) is not in the required format.It must either be set to "None" or conform to thefollowing format (in-line spaces are literal):<digits> <unit> I+D <on|off> chip per <whatever>for a unified cache, or<digits> <unit> I + <digits> <unit> D <on|off> chip per <whatever>or<digits> <unit> I <on|off> chip per <whatever>[optional text]; <digits> <unit> D <on|off> chip per <whatever>[optional text]for split caches.Acceptable values for <unit> are KB, MB, GB, or TB.No value for hw_tcache was specified.- The "license_num" field is invalid.It must be numeric, with or without a leading or trailing "A".The current value is "nnn (Your SPEC license number)".- The "notes_*.*?_*" field (any field matching "notes_*.*?_*\d+") is missing.- The "power_management" field is invalid.This field is used to briefly summarize any non-default settings forpower management, whether set in BIOS, firmware, operating system, orelsewhere.Details of the settings are in the power notes section of the result.- The "sw_avail" field is invalid.It must be MMM-YYYY, where YYYY is the full four digityear, and MMM is the three-letter English month abbreviation.- The "sw_other" field is invalid.The value must be non-blank and may not begin with "--".If you are not using any other software relevant to SPECCPU performance, you must say "None" here.The log for this run is in /home/speccpu/cpu2017/result/CPU2017.009.logruncpu finished at 2023-07-05 15:06:45; 11441 total seconds elapsed

结果

 

 

 

错误处理

警告Version check returned "1.1.7 1613543369" NOTICE: Your version, 1.0.5, is not the newest

SPEC CPU(r) 2017 Benchmark Suites
Copyright 1995-2017 Standard Performance Evaluation Corporation (SPEC)runcpu v5825
Using 'linux-x86_64' tools
Reading file manifests... read 32272 entries from 2 files in 0.08s (399173 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 53 benchsets.
Reading config file '/home/speccpu/cpu2017/config/gcc.cfg'
2 configurations selected:Action    Run Mode   Workload     Report Type      Benchmarks
--------   --------   --------   ----------------   ---------------------------
validate   rate       refrate    SPECrate2017_int   intrate                    
validate   rate       refrate    SPECrate2017_fp    fprate                     
Loading "http://www.spec.org/auto/cpu2017/current_version" for version check...
OKVersion check returned "1.1.7 1613543369"
NOTICE: Your version, 1.0.5, is not the newestVersion 1.1.7 was released on 2021-02-17 14:29:29Use 'runcpu --update' to get the new version.  For more info, see:https://www.spec.org/cpu2017/Docs/runcpu.html#update----------------------------------The run will continue in 5 seconds----------------------------------

在线更新 SPEC CPU 2017

runcpu --update

日志

(base) yeqiang@yeqiang-MS-7B23:/home/speccpu/cpu2017$ runcpu --update
SPEC CPU(r) 2017 Benchmark Suites
Copyright 1995-2017 Standard Performance Evaluation Corporation (SPEC)runcpu v5825
Using 'linux-x86_64' tools
Reading file manifests... read 32272 entries from 2 files in 0.08s (402042 files/s)
Loading runcpu modules.................
Locating benchmarks...found 47 benchmarks in 53 benchsets.CPU2017 update mode selected
Downloading update information...Selected update:From v1.0.5 to v1.1.9Update size: 35 MBDownloading update metadata: 6745 B (18 KB/s)
Update metadata parsed successfully.Update summary:Files to remove: 21Directories to remove: 0Files to change: 584Files to add: 101
Update metadata downloaded and verified.Checking files that will be changed or removed by the update...
Checks completed.
Update: Downloading update: 35 MB/35 MB (100%; 1982 KB/s))
Update downloaded and verified.Uncompressing update fileProceed with update? (y/n)
ySuite update successful!There is no log file for this run.runcpu finished at 2023-07-03 14:55:49; 80 total seconds elapsed

Error with make.diffwrf_521 'specmake --output-sync --jobs=8 build TARGET=diffwrf_521'

  Building 521.wrf_r base mytest-m64: (build_base_mytest-m64.0000) [2023-07-05 10:56:29]
Error with make.diffwrf_521 'specmake --output-sync --jobs=8 build TARGET=diffwrf_521':----------------------------------------------------------------------------Please review this file:"/home/speccpu/cpu2017/benchspec/CPU/521.wrf_r/build/build_base_mytest-m64.0000/make.diffwrf_521.out"----------------------------------------------------------------------------Command returned exit code 2Error with make!
*** Error building 521.wrf_r base
The log for this run is in /home/speccpu/cpu2017/result/CPU2017.007.log
The debug log for this run is in /home/speccpu/cpu2017/result/CPU2017.007.log.debug
*
* Temporary files were NOT deleted; keeping temporaries such as
* /home/speccpu/cpu2017/result/CPU2017.007.log.debug and
* /home/speccpu/cpu2017/tmp/CPU2017.007
* (These may be large!)
*
runcpu finished at 2023-07-05 10:56:39; 8858 total seconds elapsed
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(4)/COMPLEX(4)).
c1fm1b.fppized.f90:87:33:85 |       call c1f5kb ( ido, l1, na, c, inc2, ch, 2, wa(iw) )|                                 286 |     else if ( nbr == 8 ) then87 |       call c1f5kb ( ido, l1, na, ch, 2, c, inc2, wa(iw) )|                                 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(4)/COMPLEX(4)).
c1fm1b.fppized.f90:91:42:89 |       call c1fgkb ( ido, ip, l1, lid, na, c, c, inc2, ch, ch, 2, wa(iw) )|                                          290 |     else if ( nbr == 10 ) then91 |       call c1fgkb ( ido, ip, l1, lid, na, ch, ch, 2, c, c, inc2, wa(iw) )|                                          1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(4)/COMPLEX(4)).
specmake: *** [/home/speccpu/cpu2017/benchspec/Makefile.defaults:386: c1fm1b.fppized.o] Error 1
specmake: *** Waiting for unfinished jobs....

参考官网解释

FAQ - CPU 2017

Build.08  q. I have GCC 10. Why are several Fortran benchmarks failing to build, complaining about "type mismatches"?

a. If you compile using GCC 10 (and presumably later) you must include -fallow-argument-mismatch. If you do not include this flag, compiling 527.cam4_r, 627.cam4_s, 521.wrf_r, 621.wrf_s, and 628.pop2_s will fail with message:

Error: Type mismatch between actual argument at (1) and actual argument at (2)

For more information, see Porting to GCC 10- GNU Project.

Note that in accordance with the same-for-all rule www.spec.org/cpu2017/Docs/runrules.html#BaseFlags it is not allowed to set -fallow-argument-mismatch as a PORTABILITY option. Instead, it must be applied to all of Base. The Example GCC config files as updated for SPEC CPU 2017 v1.1.5 obey this rule.

原因gcc版本11.4.0已经大于gcc 10,虽然gcc.cfg有配置,但没有生效

删掉 ifdef endif判断,保留中间EXTRA_FFLAGS = -fallow-argument-mismatch


http://www.ppmy.cn/news/762529.html

相关文章

Android OTG的了解

工作中要用到OTG的功能&#xff0c;今天花时间了解了一下&#xff0c;在此做一个简短的总结。 OTG是on - the - go的缩写&#xff0c;主要应用于各种不同的设备或移动设备间的连接&#xff0c;进行数据交换。这是otg的功能&#xff0c;即是数据交换。 可是怎么用OTG功能呢&…

Android USB OTG功能如何打开及实现

前言 欢迎大家我分享和推荐好用的代码段~~ 声明 欢迎转载&#xff0c;但请保留文章原始出处&#xff1a; CSDN&#xff1a;http://www.csdn.net 雨季o莫忧离&#xff1a;http://blog.csdn.net/luckkof 正文 USB OTG功能如何打开及实现 US…

OTG – Android USB Hos

前几天研究了一下Android上OTG的功能。 OTG在Android3.1及以上被支持。也就是minSdkVersion为12. API概述 UsbManager 允许您枚举已连接的USB设备并且与其进行“交流”。 UsbDevice 代表了一个已连接的USB的设备并且包含具有该设备验证信息&#xff0c;接口和接入点的方法。 Us…

OTG协议

我们的网关使用OTG协议传输数据进行固件烧写&#xff0c;所以就来了解下OTG协议是什么。 OTG是On-The-Go的缩写&#xff0c;是近年发展起来的技术。2001年12月18日由USB标准化组织公布&#xff0c;主要应用于不同的设备或移动设备间的联接&#xff0c;进行数据交换。 OTG改善了…

OTG硬件检测电路

OTG硬件检测电路 文章目录 OTG硬件检测电路1. OTG接口与转换器1.1 Micro USB1.2 Type C 2. OTG接口电路2.1 Micro USB2.2 Type C 致谢 1. OTG接口与转换器 OTG是"On The Go"的英文缩写&#xff0c;字面上可以理解为“安上即可用”。USB传输是主从结构&#xff0c;一切…

TYPE-C接口设备OTG线(手机接OTG线的同时进行充电)

如何实现这种让Type-c接口设备实现充电的同时又能实现数据传输&#xff08;OTG&#xff09;的功能&#xff08;充电数据传输的方案&#xff09;这你就用到一颗PD协议芯片来配置了 ,乐得瑞推出LDR6023S可完整兼容各种手机疑难杂症的兼容性问题。 LDR6023规格书资料 参考设计电…

Android OTG 读写U盘文件

最近项目需要做一个关于OTG的功能&#xff0c;其实也就使用到U盘的文件读取&#xff0c;一般这种需求是不需要的&#xff0c;因为大部分的系统都会自动挂载U盘&#xff0c;但是个别系统还是需要自己去实现&#xff0c;查了很多资料都没有找到一个完整的能用的例子&#xff0c;要…

USB OTG连接方式

1. 概要 OTG设备使用插头中的ID引脚来区分A/B Device&#xff0c;ID接地被称作为A-Device,充当USB Host&#xff0c;A-Device始终为总线 提供电力&#xff0c;ID悬空被称作为B-Device,充当USB Device&#xff0c;设备的USB Host/USB Device角色可以通过HNP(主机交换 协议)切换。…