summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEric Christopher <echristo@apple.com>2010-06-18 22:51:25 +0000
committerEric Christopher <echristo@apple.com>2010-06-18 22:51:25 +0000
commit69a462ef710b01ee8781dbf814b7088b302d506a (patch)
treef851570861640c9b6252601276d15b138cb16fc1 /docs
parent68741be5e6a4a0e633928e4d86eea38aa07a2ca0 (diff)
downloadllvm-69a462ef710b01ee8781dbf814b7088b302d506a.tar.gz
llvm-69a462ef710b01ee8781dbf814b7088b302d506a.tar.bz2
llvm-69a462ef710b01ee8781dbf814b7088b302d506a.tar.xz
Another typo.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@106340 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/DebuggingJITedCode.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/DebuggingJITedCode.html b/docs/DebuggingJITedCode.html
index adca01d88c..83acbe439b 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