diff options
| author | Chris Lattner <sabre@nondot.org> | 2007-12-29 01:05:01 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2007-12-29 01:05:01 +0000 |
| commit | 7cafd92aa991bad540cc34c24a1a811fbb4ae223 (patch) | |
| tree | 9a1b4ece57cf6d2959d6cecda94591ca70f830fc | |
| parent | e96658392d4da29ec8aa53db28c67257e3b77077 (diff) | |
| download | bcm5719-llvm-7cafd92aa991bad540cc34c24a1a811fbb4ae223.tar.gz bcm5719-llvm-7cafd92aa991bad540cc34c24a1a811fbb4ae223.zip | |
expand note.
llvm-svn: 45393
| -rw-r--r-- | llvm/lib/Target/README.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/llvm/lib/Target/README.txt b/llvm/lib/Target/README.txt index 2ef77cb8d30..1f7b3c8cd06 100644 --- a/llvm/lib/Target/README.txt +++ b/llvm/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. //===---------------------------------------------------------------------===// |
