summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEvan Cheng <evan.cheng@apple.com>2007-10-08 17:54:24 +0000
committerEvan Cheng <evan.cheng@apple.com>2007-10-08 17:54:24 +0000
commit4c73befe28b59b7112cee2881e3b82768c9aabb7 (patch)
tree340bb7eff237d040c1066bf0c695101d24a3adc5
parentacc8b68e5f3587695e317bea8cad1795a0b290b6 (diff)
downloadbcm5719-llvm-4c73befe28b59b7112cee2881e3b82768c9aabb7.tar.gz
bcm5719-llvm-4c73befe28b59b7112cee2881e3b82768c9aabb7.zip
LLVM does not use the old style simple isel any more.
llvm-svn: 42758
-rw-r--r--llvm/docs/CodeGenerator.html7
1 files changed, 2 insertions, 5 deletions
diff --git a/llvm/docs/CodeGenerator.html b/llvm/docs/CodeGenerator.html
index bc82b46735b..b454b6b9d0b 100644
--- a/llvm/docs/CodeGenerator.html
+++ b/llvm/docs/CodeGenerator.html
@@ -748,11 +748,8 @@ explains how they work and some of the rationale behind their design.</p>
<p>
Instruction Selection is the process of translating LLVM code presented to the
code generator into target-specific machine instructions. There are several
-well-known ways to do this in the literature. In LLVM there are two main forms:
-the SelectionDAG based instruction selector framework and an old-style 'simple'
-instruction selector, which effectively peephole selects each LLVM instruction
-into a series of machine instructions. We recommend that all targets use the
-SelectionDAG infrastructure.
+well-known ways to do this in the literature. LLVM uses a SelectionDAG based
+instruction selector.
</p>
<p>Portions of the DAG instruction selector are generated from the target
OpenPOWER on IntegriCloud