adec922361
We would like to start pushing -mcpu=generic towards enabling the set of features that improves performance for some CPUs, without hurting any others. A blend of the performance options hopefully beneficial to all CPUs. The largest part of that is enabling in-order scheduling using the Cortex-A55 schedule model. This is similar to the Arm backend change from eecb353d0e25ba which made -mcpu=generic perform in-order scheduling using the cortex-a8 schedule model. The idea is that in-order cpu's require the most help in instruction scheduling, whereas out-of-order cpus can for the most part out-of-order schedule around different codegen. Our benchmarking suggests that hypothesis holds. When running on an in-order core this improved performance by 3.8% geomean on a set of DSP workloads, 2% geomean on some other embedded benchmark and between 1% and 1.8% on a set of singlecore and multicore workloads, all running on a Cortex-A55 cluster. On an out-of-order cpu the results are a lot more noisy but show flat performance or an improvement. On the set of DSP and embedded benchmarks, run on a Cortex-A78 there was a very noisy 1% speed improvement. Using the most detailed results I could find, SPEC2006 runs on a Neoverse N1 show a small increase in instruction count (+0.127%), but a decrease in cycle counts (-0.155%, on average). The instruction count is very low noise, the cycle count is more noisy with a 0.15% decrease not being significant. SPEC2k17 shows a small decrease (-0.2%) in instruction count leading to a -0.296% decrease in cycle count. These results are within noise margins but tend to show a small improvement in general. When specifying an Apple target, clang will set "-target-cpu apple-a7" on the command line, so should not be affected by this change when running from clang. This also doesn't enable more runtime unrolling like -mcpu=cortex-a55 does, only changing the schedule used. A lot of existing tests have updated. This is a summary of the important differences: - Most changes are the same instructions in a different order. - Sometimes this leads to very minor inefficiencies, such as requiring an extra mov to move variables into r0/v0 for the return value of a test function. - misched-fusion.ll was no longer fusing the pairs of instructions it should, as per D110561. I've changed the schedule used in the test for now. - neon-mla-mls.ll now uses "mul; sub" as opposed to "neg; mla" due to the different latencies. This seems fine to me. - Some SVE tests do not always remove movprfx where they did before due to different register allocation giving different destructive forms. - The tests argument-blocks-array-of-struct.ll and arm64-windows-calls.ll produce two LDR where they previously produced an LDP due to store-pair-suppress kicking in. - arm64-ldp.ll and arm64-neon-copy.ll are missing pre/postinc on LPD. - Some tests such as arm64-neon-mul-div.ll and ragreedy-local-interval-cost.ll have more, less or just different spilling. - In aarch64_generated_funcs.ll.generated.expected one part of the function is no longer outlined. Interestingly if I switch this to use any other scheduled even less is outlined. Some of these are expected to happen, such as differences in outlining or register spilling. There will be places where these result in worse codegen, places where they are better, with the SPEC instruction counts suggesting it is not a decrease overall, on average. Differential Revision: https://reviews.llvm.org/D110830
49 lines
1.5 KiB
LLVM
49 lines
1.5 KiB
LLVM
; RUN: llc -o - %s -mtriple=aarch64-unknown -aarch64-enable-cond-br-tune=false -mcpu=cortex-a57 -mattr=+arith-bcc-fusion | FileCheck %s --check-prefix=FUSEBCC
|
|
; RUN: llc -o - %s -mtriple=aarch64-unknown -aarch64-enable-cond-br-tune=false -mcpu=cortex-a57 -mattr=+arith-cbz-fusion | FileCheck %s --check-prefix=FUSECBZ
|
|
; RUN: llc -o - %s -mtriple=aarch64-unknown -aarch64-enable-cond-br-tune=false -mcpu=cyclone | FileCheck %s --check-prefix=FUSEBCC --check-prefix=FUSECBZ
|
|
|
|
target triple = "aarch64-unknown"
|
|
|
|
declare void @foobar(i32 %v0, i32 %v1)
|
|
|
|
; Make sure cmp is scheduled in front of bcc
|
|
; FUSEBCC-LABEL: test_cmp_bcc:
|
|
; FUSEBCC: cmp {{w[0-9]+}}, #13
|
|
; FUSEBCC-NEXT: b.ne {{.?LBB[0-9_]+}}
|
|
define void @test_cmp_bcc(i32 %a0, i32 %a1) {
|
|
entry:
|
|
%cond = icmp eq i32 %a0, 13
|
|
%v1 = add i32 %a1, 7
|
|
br i1 %cond, label %if, label %exit
|
|
|
|
if:
|
|
call void @foobar(i32 %v1, i32 %a0)
|
|
br label %exit
|
|
|
|
exit:
|
|
call void @foobar(i32 %a0, i32 %v1)
|
|
ret void
|
|
}
|
|
|
|
; Make sure sub is scheduled in front of cbnz
|
|
; FUSECBZ-LABEL: test_sub_cbz:
|
|
; FUSECBZ: sub [[R:w[0-9]+]], {{w[0-9]+}}, #13
|
|
; FUSECBZ-NEXT: cbnz [[R]], {{.?LBB[0-9_]+}}
|
|
define void @test_sub_cbz(i32 %a0, i32 %a1) {
|
|
entry:
|
|
; except for the fusion opportunity the sub/add should be equal so the
|
|
; scheduler would leave them in source order if it weren't for the scheduling
|
|
%v0 = sub i32 %a0, 13
|
|
%cond = icmp eq i32 %v0, 0
|
|
%v1 = add i32 %a1, 7
|
|
br i1 %cond, label %if, label %exit
|
|
|
|
if:
|
|
call void @foobar(i32 %v1, i32 %v0)
|
|
br label %exit
|
|
|
|
exit:
|
|
call void @foobar(i32 %v0, i32 %v1)
|
|
ret void
|
|
}
|