From 9500a6ec2e58b01bd9a67e13b1f22cf62b5096d7 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Fri, 15 Oct 2004 17:04:28 +0000 Subject: Fix broken links git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@17016 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/Bugpoint.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/Bugpoint.html') diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html index 0fc16b710a..19dd0ea3c3 100644 --- a/docs/Bugpoint.html +++ b/docs/Bugpoint.html @@ -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

-- cgit v1.2.3