6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-01-12 17:32:19 +00:00
Code Issues Projects Releases Wiki Activity

Two minor fixes

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9256 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2003-10-19 17:27:12 +00:00
parent 237b366564
commit 129e7a88b0
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/CommandGuide/bugpoint.html
View File

@ -27,7 +27,7 @@ crash, and reduce the file down to a small example which triggers the crash.<p>
<a name="designphilosophy">
<h4>Design Philosophy</h4>
<tt>bugpoint</tt> has been designed to be a useful tool without requiring any
<tt>bugpoint</tt> is designed to be a useful tool without requiring any
hooks into the LLVM infrastructure at all. It works with any and all LLVM
passes and code generators, and does not need to "know" how they work. Because
of this, it may appear to do a lot of stupid things or miss obvious
@ -70,7 +70,7 @@ If an optimizer crashes, <tt>bugpoint</tt> will try as hard as it can to
reduce the list of passes and the size of the test program. First,
<tt>bugpoint</tt> figures out which combination of passes triggers the bug. This
is useful when debugging a problem exposed by <tt>gccas</tt>, for example,
because it runs over 30 optimizations.<p>
because it runs over 25 optimizations.<p>
Next, <tt>bugpoint</tt> tries removing functions from the module, to reduce the
size of the test program. Usually it is able to reduce a test program