Changes in directory llvm/lib/Target/ARM:
README.txt updated: 1.23 -> 1.24
---
Log message:
Remove item: thumb padding in constant islands
---
Diffs of the changes: (+2 -6)
README.txt | 8 ++------
1 files changed, 2 insertions(+), 6 deletions(-)
Index: llvm/lib/Target/ARM/README.txt
diff -u llvm/lib/Target/ARM/README.txt:1.23 llvm/lib/Target/ARM/README.txt:1.24
--- llvm/lib/Target/ARM/README.txt:1.23 Fri Apr 20 15:18:43 2007
+++ llvm/lib/Target/ARM/README.txt Sun Apr 29 19:32:06 2007
@@ -35,14 +35,10 @@
1. There may be some advantage to trying to be smarter about the initial
placement, rather than putting everything at the end.
-2. The handling of 2-byte padding for Thumb is overly conservative. There
-would be a small gain to keeping accurate track of the padding (which would
-require aligning functions containing constant pools to 4-byte boundaries).
-
-3. There might be some compile-time efficiency to be had by representing
+2. There might be some compile-time efficiency to be had by representing
consecutive islands as a single block rather than multiple blocks.
-4. Use a priority queue to sort constant pool users in inverse order of
+3. Use a priority queue to sort constant pool users in inverse order of
position so we always process the one closed to the end of functions
first. This may simply CreateNewWater.
_______________________________________________
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
