summaryrefslogtreecommitdiff
path: root/lib/Target/README.txt
diff options
context:
space:
mode:
authorEli Friedman <eli.friedman@gmail.com>2011-03-21 01:33:03 +0000
committerEli Friedman <eli.friedman@gmail.com>2011-03-21 01:33:03 +0000
commitddfa02ba248c981ed346708ee3a80d834b684f97 (patch)
tree50d1b0e885fd38ce42639f5be683da025d715d43 /lib/Target/README.txt
parent485fafc8406db8552ba5e3ff871a6ee32694ad90 (diff)
downloadllvm-ddfa02ba248c981ed346708ee3a80d834b684f97.tar.gz
llvm-ddfa02ba248c981ed346708ee3a80d834b684f97.tar.bz2
llvm-ddfa02ba248c981ed346708ee3a80d834b684f97.tar.xz
This README entry was fixed recently.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@127982 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Target/README.txt')
-rw-r--r--lib/Target/README.txt28
1 files changed, 0 insertions, 28 deletions
diff --git a/lib/Target/README.txt b/lib/Target/README.txt
index 45da3ddb60..63f1f79962 100644
--- a/lib/Target/README.txt
+++ b/lib/Target/README.txt
@@ -392,34 +392,6 @@ PHI Slicing could be extended to do this.
//===---------------------------------------------------------------------===//
-LSR should know what GPR types a target has from TargetData. This code:
-
-volatile short X, Y; // globals
-
-void foo(int N) {
- int i;
- for (i = 0; i < N; i++) { X = i; Y = i*4; }
-}
-
-produces two near identical IV's (after promotion) on PPC/ARM:
-
-LBB1_2:
- ldr r3, LCPI1_0
- ldr r3, [r3]
- strh r2, [r3]
- ldr r3, LCPI1_1
- ldr r3, [r3]
- strh r1, [r3]
- add r1, r1, #4
- add r2, r2, #1 <- [0,+,1]
- sub r0, r0, #1 <- [0,-,1]
- cmp r0, #0
- bne LBB1_2
-
-LSR should reuse the "+" IV for the exit test.
-
-//===---------------------------------------------------------------------===//
-
Tail call elim should be more aggressive, checking to see if the call is
followed by an uncond branch to an exit block.