MemorySSA: Fix example in header comment.

This fixes the example so that it matches the pass's behavior. I was a
little confused by the example until I tried running it and realized that
there was a mistake.

Differential Revision: http://reviews.llvm.org/D20657

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@270811 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/include/llvm/Transforms/Utils/MemorySSA.h b/include/llvm/Transforms/Utils/MemorySSA.h
index 2de3192..b6de7a9 100644 (file)
--- a/include/llvm/Transforms/Utils/MemorySSA.h
+++ b/include/llvm/Transforms/Utils/MemorySSA.h
@@ -45,9 +45,9 @@
 //   store i32 5, i32* %2, align 4
 //   ; 4 = MemoryDef(3)
 //   store i32 7, i32* %4, align 4
-//   ; MemoryUse(4)
-//   %7 = load i32* %2, align 4
 //   ; MemoryUse(3)
+//   %7 = load i32* %2, align 4
+//   ; MemoryUse(4)
 //   %8 = load i32* %4, align 4
 //   %add = add nsw i32 %7, %8
 //   ret i32 %add
@@ -59,7 +59,7 @@
 //
 // Each def also has a list of users associated with it, so you can walk from
 // both def to users, and users to defs. Note that we disambiguate MemoryUses,
-// but not the RHS of MemoryDefs. You can see this above at %8, which would
+// but not the RHS of MemoryDefs. You can see this above at %7, which would
 // otherwise be a MemoryUse(4). Being disambiguated means that for a given
 // store, all the MemoryUses on its use lists are may-aliases of that store (but
 // the MemoryDefs on its use list may not be).