From: Eric Christopher <echristo@apple.com>
Date: Fri, 18 Jun 2010 22:51:25 +0000 (+0000)
Subject: Another typo.
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=69a462ef710b01ee8781dbf814b7088b302d506a;p=oota-llvm.git

Another typo.


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

diff --git a/docs/DebuggingJITedCode.html b/docs/DebuggingJITedCode.html
index adca01d88c4..83acbe439bb 100644
--- a/docs/DebuggingJITedCode.html
+++ b/docs/DebuggingJITedCode.html
@@ -28,7 +28,7 @@ no such file to look for.
 
 <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