From 5706f25694ac2042e6d6a2542771dff37d9bcc45 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Thu, 1 Jul 2004 20:41:43 +0000 Subject: [PATCH] Fix broken links git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14548 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/Bugpoint.html | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html index 519e02d5277..0fc16b710aa 100644 --- a/docs/Bugpoint.html +++ b/docs/Bugpoint.html @@ -12,7 +12,7 @@

SYNOPSIS

bugpoint [options] [input LLVM ll/bc files] [LLVM passes] --args <program arguments>... - +

DESCRIPTION

The bugpoint tool narrows down the source of @@ -20,7 +20,7 @@ problems in LLVM tools and 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 gccas crashes while optimizing a file, it +if gccas 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.

@@ -84,8 +84,8 @@ flow graph, to reduce the size of the function as much as possible. Finally, bugpoint deletes any individual LLVM instructions whose absence does not eliminate the failure. At the end, bugpoint should tell you what passes crash, give you a bytecode file, and give you instructions on how to -reproduce the failure with opt, analyze, or llc.

+reproduce the failure with opt, analyze, or llc.

Code generator debugger

@@ -239,10 +239,6 @@ non-obvious ways. Here are some hints and tips:

If bugpoint succeeds in finding a problem, it will exit with 0. Otherwise, if an error occurs, it will exit with a non-zero value. -

SEE ALSO

-opt, -analyze -
Maintained by the LLVM Team. -- 2.34.1