summaryrefslogtreecommitdiffstats
path: root/llvm/docs/DebuggingJITedCode.html
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
commita4f06da5f10df0b5db322e2144ded5cc7fdfe8c9 (patch)
treed9b4359d90dcc4acffcc55c888bc3ccb0a25acb6 /llvm/docs/DebuggingJITedCode.html
parentc0fe8429f269cd51d80b60243d33b8f2e8b7c891 (diff)
downloadbcm5719-llvm-a4f06da5f10df0b5db322e2144ded5cc7fdfe8c9.tar.gz
bcm5719-llvm-a4f06da5f10df0b5db322e2144ded5cc7fdfe8c9.zip
Another typo.
llvm-svn: 106340
Diffstat (limited to 'llvm/docs/DebuggingJITedCode.html')
-rw-r--r--llvm/docs/DebuggingJITedCode.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/DebuggingJITedCode.html b/llvm/docs/DebuggingJITedCode.html
index adca01d88c4..83acbe439bb 100644
--- a/llvm/docs/DebuggingJITedCode.html
+++ b/llvm/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
OpenPOWER on IntegriCloud