[llvm-commits] CVS: llvm/docs/CommandGuide/bugpoint.pod

[Misha Brukman]

Changes in directory llvm/docs/CommandGuide:

bugpoint.pod updated: 1.1 -> 1.2

---
Log message:

Simplify wording: `the bugpoint tool' can just become `bugpoint'.


---
Diffs of the changes:  (+7 -7)

Index: llvm/docs/CommandGuide/bugpoint.pod
diff -u llvm/docs/CommandGuide/bugpoint.pod:1.1 llvm/docs/CommandGuide/bugpoint.pod:1.2
--- llvm/docs/CommandGuide/bugpoint.pod:1.1	Thu Jul  1 15:29:08 2004
+++ llvm/docs/CommandGuide/bugpoint.pod	Fri Jul  2 10:36:29 2004
@@ -11,13 +11,13 @@
 
 =head1 DESCRIPTION
 
-The B<bugpoint> 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<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.
+B<bugpoint> 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<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.
 
 =head2 Design Philosophy