-<p>A miscompilation occurs when a pass does not correctly transform a program,
-thus producing errors that are only noticed during execution. This is different
-from producing invalid LLVM code (i.e., code not in SSA form, using values
-before defining them, etc.) which the verifier will check for after a pass
-finishes its run.</p>
-
-<p>If it looks like the LLVM compiler is miscompiling a program, the very first
-thing to check is to make sure it is not using undefined behavior. In
-particular, check to see if the program <a
-href="http://valgrind.kde.org/">valgrind</a>s clean, passes purify, or some
-other memory checker tool. Many of the "LLVM bugs" that we have chased down
-ended up being bugs in the program being compiled, not LLVM.</p>
+<p>If llvm-gcc successfully produces an executable, but that executable doesn't
+run right, this is either a bug in the code or a bug in the
+compiler. The first thing to check is to make sure it is not using undefined
+behavior (e.g. reading a variable before it is defined). In particular, check
+to see if the program <a href="http://valgrind.org/">valgrind</a>s clean,
+passes purify, or some other memory checker tool. Many of the "LLVM bugs" that
+we have chased down ended up being bugs in the program being compiled, not
+ LLVM.</p>