From 83ec4b6711980242ef3c55a4fa36b2d7a39c1bfb Mon Sep 17 00:00:00 2001
From: Duncan Sands
Date: Fri, 6 Jun 2008 12:08:01 +0000
Subject: Wrap MVT::ValueType in a struct to get type safety and better control
the abstraction. Rename the type to MVT. To update out-of-tree patches, the
main thing to do is to rename MVT::ValueType to MVT, and rewrite expressions
like MVT::getSizeInBits(VT) in the form VT.getSizeInBits(). Use
VT.getSimpleVT() to extract a MVT::SimpleValueType for use in switch
statements (you will get an assert failure if VT is an extended value type -
these shouldn't exist after type legalization). This results in a small
speedup of codegen and no new testsuite failures (x86-64 linux).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@52044 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/CodeGenerator.html | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
(limited to 'docs')
diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html
index bcbb64cafb..a283981c7c 100644
--- a/docs/CodeGenerator.html
+++ b/docs/CodeGenerator.html
@@ -790,7 +790,8 @@ to the node defining the used value. Because nodes may define multiple values,
edges are represented by instances of the SDOperand class, which is
a <SDNode, unsigned> pair, indicating the node and result
value being used, respectively. Each value produced by an SDNode has
-an associated MVT::ValueType indicating what type the value is.
+an associated MVT (Machine Value Type) indicating what the type of the
+value is.
SelectionDAGs contain two different kinds of values: those that represent
data flow and those that represent control flow dependencies. Data values are
--
cgit v1.2.3