[llvm-bugs] [Bug 27454] New: [Cyclone] Register spills related to FeatureZCZeroing
via llvm-bugs
llvm-bugs at lists.llvm.org
Thu Apr 21 14:18:58 PDT 2016
https://llvm.org/bugs/show_bug.cgi?id=27454
Bug ID: 27454
Summary: [Cyclone] Register spills related to FeatureZCZeroing
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Backend: AArch64
Assignee: unassignedbugs at nondot.org
Reporter: haicheng at codeaurora.org
CC: gberry at codeaurora.org, llvm-bugs at lists.llvm.org,
mcrosier at codeaurora.org
Classification: Unclassified
Created attachment 16245
--> https://llvm.org/bugs/attachment.cgi?id=16245&action=edit
a .ll test case that has extra register spills if using -mcpu=cyclone
I am trying to port FeatureZCZeroing from Cyclone to Kryo. Using immediate #0
to zero out W and X registers works great in Kryo. But using #0 to zero out
float registers sometimes causes extra register spills or move instructions on
either Cyclone or Kryo.
I attached a reduced IR test case which basically corresponds to the following
C code
double foo(int n) {
double r=-10000;
for (int i=0;i<n;i++) {
x = sin(i);
r = max(r,x);
}
return(-r);
}
If compiled towards Cyclone, the loop body has one spill and two reloads as
below
.LBB0_1: // %for.body
// =>This Inner Loop Header: Depth=1
str q0, [sp] // 16-byte Folded Spill
ldr q0, [sp] // 16-byte Folded Reload
bl sin
fmaxnm d8, d8, d0
ldr q0, [sp] // 16-byte Folded Reload
fadd d0, d0, d9
add w20, w20, #1 // =1
cmp w20, w19
b.lt .LBB0_1
If FeatureZCZeroing is disabled (together with FeatureZCRegMove) on Cyclone,
the translated assembly does not have these load/store instructions:
.LBB0_1: // %for.body
// =>This Inner Loop Header: Depth=1
mov v0.16b, v8.16b
bl sin
fmaxnm d9, d9, d0
fadd d8, d8, d10
add w20, w20, #1 // =1
cmp w20, w19
b.lt .LBB0_1
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160421/0429a373/attachment.html>
More information about the llvm-bugs
mailing list