[Hexagon] Use correct offset when extracting from the high word

When extracting a bitfield from the high register in a register pair,
the final offset should be relative to the high register (for 32-bit
extracts).

llvm-svn: 297288
This commit is contained in:
Krzysztof Parzyszek 2017-03-08 15:46:28 +00:00
parent 76b6bd355d
commit 1b7197e690
2 changed files with 24 additions and 0 deletions

View File

@ -2480,6 +2480,7 @@ bool BitSimplification::simplifyExtractLow(MachineInstr *MI,
continue;
if (RW != SW)
SR = (Off/RW == 0) ? Hexagon::isub_lo : Hexagon::isub_hi;
Off = Off % RW;
if (!validateReg({R,SR}, ExtOpc, 1))
continue;

View File

@ -0,0 +1,23 @@
; RUN: llc -march=hexagon < %s | FileCheck %s
; CHECK: extractu(r1,#31,#0)
; In the IR this was an extract of 31 bits starting at position 32 in r1:0.
; When mapping it to an extract from r1, the offset was not reset to 0, and
; we had "extractu(r1,#31,#32)".
target triple = "hexagon"
define hidden i32 @fred([101 x double]* %a0, i32 %a1, i32* %a2, i32* %a3) #0 {
b4:
br label %b5
b5: ; preds = %b5, %b4
%v6 = call double @fabs(double undef) #1
store double %v6, double* undef, align 8
br label %b5
}
declare double @fabs(double) #1
attributes #0 = { nounwind "target-cpu"="hexagonv60" "target-features"="-hvx,-hvx-double,-long-calls" }
attributes #1 = { nounwind readnone "target-cpu"="hexagonv60" "target-features"="-hvx,-hvx-double,-long-calls" }