Continue refactoring inline asm code. If there is an earlyclobber output

[oota-llvm.git] / docs / CommandLine.html

diff --git a/docs/CommandLine.html b/docs/CommandLine.html
index 5898bb31137e71605110e0519a5e3980a2029c16..8358d8756e196f4ae5c53e6ff0834183cba02a60 100644 (file)
--- a/docs/CommandLine.html
+++ b/docs/CommandLine.html
@@ -1042,7 +1042,7 @@ extern bool DebugFlag;
 // debug build, then the code specified as the option to the macro will be
 // executed.  Otherwise it will not be.  Example:
 //
-// DEBUG(std::cerr << "Bitset contains: " << Bitset << "\n");
+// DOUT << "Bitset contains: " << Bitset << "\n";
 //</i>
 <span class="doc_hilite">#ifdef NDEBUG
 #define DEBUG(X)
@@ -1763,7 +1763,7 @@ your custom data type.<p>
 <p>This approach has the advantage that users of your custom data type will
 automatically use your custom parser whenever they define an option with a value
 type of your data type.  The disadvantage of this approach is that it doesn't
-work if your fundemental data type is something that is already supported.</p>
+work if your fundamental data type is something that is already supported.</p>
 
 </li>