search for: gcc_r

...ss did not yield performance improvements on google workloads. SPECInt 2017 We evaluated the impact of the machine function splitter on SPECInt 2017 using the int rate metrics. Overall, we found a 1.6% geomean intrate improvement for the benchmarks where performance improved (500.perlbench_r, 502.gcc_r, 505.mcf_r, 520.omnetpp_r). For the benchmarks that didn’t improve performance, the average degradation was 0.6% (523.xalancbmk_r, 525.x264_r, 531.deepsjeng_r, 541.leela_r). We note that the instruction footprint of SPEC workloads are smaller than most modern workloads and our work is primarily fo...

...s did not yield performance improvements on google workloads. SPECInt 2017 We evaluated the impact of the machine function splitter on SPECInt 2017 using the int rate metrics. Overall, we found a 1.6% geomean intrate improvement for the benchmarks where performance improved (500.perlbench_r, 502.gcc_r, 505.mcf_r, 520.omnetpp_r). For the benchmarks that didn’t improve performance, the average degradation was 0.6% (523.xalancbmk_r, 525.x264_r, 531.deepsjeng_r, 541.leela_r). We note that the instruction footprint of SPEC workloads are smaller than most modern workloads and our work is primarily f...

.... >> >> SPECInt 2017 >> >> We evaluated the impact of the machine function splitter on SPECInt 2017 >> using the int rate metrics. Overall, we found a 1.6% geomean intrate >> improvement for the benchmarks where performance improved (500.perlbench_r, >> 502.gcc_r, 505.mcf_r, 520.omnetpp_r). For the benchmarks that didn’t >> improve performance, the average degradation was 0.6% (523.xalancbmk_r, >> 525.x264_r, 531.deepsjeng_r, 541.leela_r). >> >> We note that the instruction footprint of SPEC workloads are smaller than >> most m...