6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-02-07 14:33:15 +00:00
Code Issues Projects Releases Wiki Activity

Clarify documentation and remove guarantees that are not fulfilled.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@132344 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Devang Patel 2011-05-31 17:45:27 +00:00
parent a9b08aa25e
commit e0bdc59321
1 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/SourceLevelDebugging.html
View File

@ -174,22 +174,15 @@ height="369">
as setting program variables, or calling functions that have been as setting program variables, or calling functions that have been
deleted.</li> deleted.</li>
<li>LLVM optimizations gracefully interact with debugging information. If
they are not aware of debug information, they are automatically disabled
as necessary in the cases that would invalidate the debug info. This
retains the LLVM features, making it easy to write new
transformations.</li>
<li>As desired, LLVM optimizations can be upgraded to be aware of the LLVM <li>As desired, LLVM optimizations can be upgraded to be aware of the LLVM
debugging information, allowing them to update the debugging information debugging information, allowing them to update the debugging information
as they perform aggressive optimizations. This means that, with effort, as they perform aggressive optimizations. This means that, with effort,
the LLVM optimizers could optimize debug code just as well as non-debug the LLVM optimizers could optimize debug code just as well as non-debug
code.</li> code.</li>
<li>LLVM debug information does not prevent many important optimizations from <li>LLVM debug information does not prevent optimizations from
happening (for example inlining, basic block reordering/merging/cleanup, happening (for example inlining, basic block reordering/merging/cleanup,
tail duplication, etc), further reducing the amount of the compiler that tail duplication, etc).<li>
eventually is "aware" of debugging information.</li>
<li>LLVM debug information is automatically optimized along with the rest of <li>LLVM debug information is automatically optimized along with the rest of
the program, using existing facilities. For example, duplicate the program, using existing facilities. For example, duplicate