From 595d32e93b3dacc143ccbe2bcabe60dcf71a3bc3 Mon Sep 17 00:00:00 2001 From: Misha Brukman Date: Fri, 2 Jul 2004 15:36:29 +0000 Subject: [PATCH] Simplify wording: `the bugpoint tool' can just become `bugpoint'. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14574 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CommandGuide/bugpoint.pod | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/CommandGuide/bugpoint.pod b/docs/CommandGuide/bugpoint.pod index d3102c7f406..8474a9b08df 100644 --- a/docs/CommandGuide/bugpoint.pod +++ b/docs/CommandGuide/bugpoint.pod @@ -11,13 +11,13 @@ I ... =head1 DESCRIPTION -The B tool narrows down the source of 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 B 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. +B narrows down the source of 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 B 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. =head2 Design Philosophy