X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FCodeGenerator.html;h=06c6e9ae04652bafba3262c3ae7454095ed948c1;hb=6fa1c051dc515b6fd1f9a26ac12fed985469bff5;hp=c09d9e1cd7022d8bbf634aa262edee3f9e04af2a;hpb=9097d14e575fa54dcf28dfd1ae0c9ebe6931dce1;p=oota-llvm.git diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html index c09d9e1cd70..06c6e9ae046 100644 --- a/docs/CodeGenerator.html +++ b/docs/CodeGenerator.html @@ -621,9 +621,9 @@ copies a virtual register into or out of a physical register when needed.

-int %test(int %X, int %Y) {
-  %Z = div int %X, %Y
-  ret int %Z
+define i32 @test(i32 %X, i32 %Y) {
+  %Z = udiv i32 %X, %Y
+  ret i32 %Z
 }
 
@@ -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 @@ -1467,12 +1468,12 @@ instance, in situations where an instruction such as %a = ADD %b

 %a = MOVE %b
-%a = ADD %a %b
+%a = ADD %a %c
 

Notice that, internally, the second instruction is represented as -ADD %a[def/use] %b. I.e., the register operand %a is +ADD %a[def/use] %c. I.e., the register operand %a is both used and defined by the instruction.