aboutsummaryrefslogtreecommitdiff
path: root/docs/Bugpoint.html
diff options
context:
space:
mode:
authorReid Spencer <rspencer@reidspencer.com>2007-02-09 15:59:08 +0000
committerReid Spencer <rspencer@reidspencer.com>2007-02-09 15:59:08 +0000
commit434262ad518dad47841189b27fb9f3943d8206b8 (patch)
tree5c5a3ebd2172b71a76f0319e54849e82cea05a47 /docs/Bugpoint.html
parent43eb96c3ef62c69ccec13e7326a5660a74483f04 (diff)
Remove references to gccld and gccas, adjusting the documentation to
mention llvm-ld and opt instead (if appropriate). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34094 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/Bugpoint.html')
-rw-r--r--docs/Bugpoint.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html
index 1f29533670..43d237d094 100644
--- a/docs/Bugpoint.html
+++ b/docs/Bugpoint.html
@@ -38,13 +38,13 @@
passes. It can be used to debug three types of failures: optimizer crashes,
miscompilations by optimizers, or bad native code generation (including problems
in the static and JIT compilers). It aims to reduce large test cases to small,
-useful ones. For example, if <tt>gccas</tt> crashes while optimizing a
+useful ones. For example, if <tt>opt</tt> crashes while optimizing a
file, it will identify the optimization (or combination of optimizations) that
causes the crash, and reduce the file down to a small example which triggers the
crash.</p>
-<p>For detailed case scenarios, such as debugging <tt>gccas</tt>,
-<tt>gccld</tt>, or one of the LLVM code generators, see <a
+<p>For detailed case scenarios, such as debugging <tt>opt</tt>,
+<tt>llvm-ld</tt>, or one of the LLVM code generators, see <a
href="HowToSubmitABug.html">How To Submit a Bug Report document</a>.</p>
</div>
@@ -114,7 +114,7 @@ Otherwise, there is no problem <tt>bugpoint</tt> can debug.</p>
as it can to reduce the list of passes (for optimizer crashes) and the size of
the test program. First, <tt>bugpoint</tt> figures out which combination of
optimizer passes triggers the bug. This is useful when debugging a problem
-exposed by <tt>gccas</tt>, for example, because it runs over 38 passes.</p>
+exposed by <tt>opt</tt>, for example, because it runs over 38 passes.</p>
<p>Next, <tt>bugpoint</tt> tries removing functions from the test program, to
reduce its size. Usually it is able to reduce a test program to a single