aboutsummaryrefslogtreecommitdiff
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
commit779493532794e32ae70a108e76fee97130aaae29 (patch)
treefcfb6461f49b801d8b7cbc1f3ad0027fdef68cb0
parentb428657504c72b5507419ce73ac9e305064ba9fb (diff)
LLVM does not use the old style simple isel any more.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@42758 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/CodeGenerator.html7
1 files changed, 2 insertions, 5 deletions
diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html
index bc82b46735..b454b6b9d0 100644
--- a/docs/CodeGenerator.html
+++ b/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