aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2007-12-29 01:05:01 +0000
committerChris Lattner <sabre@nondot.org>2007-12-29 01:05:01 +0000
commit92c06a01de63a94476f956101a28828c3f55adee (patch)
tree6ebcebbebe96804d2fdb68d12d4e6df0e90b1d7e
parent741c0aea08feab0ebd1932aaa8dd38836b2073ea (diff)
downloadexternal_llvm-92c06a01de63a94476f956101a28828c3f55adee.zip
external_llvm-92c06a01de63a94476f956101a28828c3f55adee.tar.gz
external_llvm-92c06a01de63a94476f956101a28828c3f55adee.tar.bz2
expand note.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@45393 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--lib/Target/README.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/lib/Target/README.txt b/lib/Target/README.txt
index 2ef77cb..1f7b3c8 100644
--- a/lib/Target/README.txt
+++ b/lib/Target/README.txt
@@ -512,6 +512,10 @@ better to sink the picbase computation down into the block for the
assertion, as it is the only one that uses it. This happens for a lot of
code with early outs.
+Another example is loads of arguments, which are usually emitted into the
+entry block on targets like x86. If not used in all paths through a
+function, they should be sunk into the ones that do.
+
In this case, whole-function-isel would also handle this.
//===---------------------------------------------------------------------===//