diff options
| author | Jakob Stoklund Olesen <stoklund@2pi.dk> | 2011-05-04 19:02:07 +0000 |
|---|---|---|
| committer | Jakob Stoklund Olesen <stoklund@2pi.dk> | 2011-05-04 19:02:07 +0000 |
| commit | 28e104bcb0d436adfc961776efb421bb21650e7b (patch) | |
| tree | a6bc8c96fa88228a0bf2599419e2b7d740c9a2f1 /test/CodeGen/Thumb2/thumb2-cmp.ll | |
| parent | 21f7902a899930bd62260ffefd610b7490c15439 (diff) | |
| download | llvm-28e104bcb0d436adfc961776efb421bb21650e7b.tar.gz llvm-28e104bcb0d436adfc961776efb421bb21650e7b.tar.bz2 llvm-28e104bcb0d436adfc961776efb421bb21650e7b.tar.xz | |
Explicitly request physreg coalesing for a bunch of Thumb2 unit tests.
These tests all follow the same pattern:
mov r2, r0
movs r0, #0
$CMP r2, r1
it eq
moveq r0, #1
bx lr
The first 'mov' can be eliminated by rematerializing 'movs r0, #0' below the
test instruction:
$CMP r0, r1
mov.w r0, #0
it eq
moveq r0, #1
bx lr
So far, only physreg coalescing can do that. The register allocators won't yet
split live ranges just to eliminate copies. They can learn, but this particular
problem is not likely to show up in real code. It only appears because r0 is
used for both the function argument and return value.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@130858 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/CodeGen/Thumb2/thumb2-cmp.ll')
| -rw-r--r-- | test/CodeGen/Thumb2/thumb2-cmp.ll | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/test/CodeGen/Thumb2/thumb2-cmp.ll b/test/CodeGen/Thumb2/thumb2-cmp.ll index 63249f4cf1..da121140be 100644 --- a/test/CodeGen/Thumb2/thumb2-cmp.ll +++ b/test/CodeGen/Thumb2/thumb2-cmp.ll @@ -1,4 +1,7 @@ -; RUN: llc < %s -march=thumb -mattr=+thumb2 | FileCheck %s +; RUN: llc < %s -march=thumb -mattr=+thumb2 -join-physregs | FileCheck %s + +; These tests implicitly depend on 'movs r0, #0' being rematerialized below the +; test as 'mov.w r0, #0'. So far, that requires physreg joining. ; 0x000000bb = 187 define i1 @f1(i32 %a) { |