[llvm-commits] [llvm] r106340 - /llvm/trunk/docs/DebuggingJITedCode.html

[Eric Christopher]

Author: echristo
Date: Fri Jun 18 17:51:25 2010
New Revision: 106340

URL: http://llvm.org/viewvc/llvm-project?rev=106340&view=rev
Log:
Another typo.

Modified:
    llvm/trunk/docs/DebuggingJITedCode.html

Modified: llvm/trunk/docs/DebuggingJITedCode.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/DebuggingJITedCode.html?rev=106340&r1=106339&r2=106340&view=diff
==============================================================================
--- llvm/trunk/docs/DebuggingJITedCode.html (original)
+++ llvm/trunk/docs/DebuggingJITedCode.html Fri Jun 18 17:51:25 2010
@@ -28,7 +28,7 @@
 
 <p>Depending on the architecture, this can impact the debugging experience in
 different ways.  For example, on most 32-bit x86 architectures, you can simply
-compile with -fno-omit-frame-pointer for GCC and -fdisable-fp-elim for LLVM.
+compile with -fno-omit-frame-pointer for GCC and -disable-fp-elim for LLVM.
 When GDB creates a backtrace, it can properly unwind the stack, but the stack
 frames owned by JITed code have ??'s instead of the appropriate symbol name.
 However, on Linux x86_64 in particular, GDB relies on the DWARF CFA debug