[llvm-commits] CVS: llvm/tools/bugpoint/BugDriver.cpp

Misha Brukman brukman at cs.uiuc.edu
Tue Apr 6 12:05:01 PDT 2004


Changes in directory llvm/tools/bugpoint:

BugDriver.cpp updated: 1.31 -> 1.32

---
Log message:

Wrap at 80 cols.


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

Index: llvm/tools/bugpoint/BugDriver.cpp
diff -u llvm/tools/bugpoint/BugDriver.cpp:1.31 llvm/tools/bugpoint/BugDriver.cpp:1.32
--- llvm/tools/bugpoint/BugDriver.cpp:1.31	Sun Mar 14 14:50:42 2004
+++ llvm/tools/bugpoint/BugDriver.cpp	Tue Apr  6 12:04:30 2004
@@ -122,13 +122,12 @@
 /// variables are set up from command line arguments.
 ///
 bool BugDriver::run() {
-  // The first thing that we must do is determine what the problem is.  Does the
-  // optimization series crash the compiler, or does it produce illegal code? We
-  // make the top-level decision by trying to run all of the passes on the the
-  // input program, which should generate a bytecode file.  If it does generate
-  // a bytecode file, then we know the compiler didn't crash, so try to diagnose
-  // a miscompilation.
-  //
+  // The first thing that we must do is determine what the problem is. Does the
+  // optimization series crash the compiler, or does it produce illegal code?
+  // We make the top-level decision by trying to run all of the passes on the
+  // the input program, which should generate a bytecode file.  If it does
+  // generate a bytecode file, then we know the compiler didn't crash, so try
+  // to diagnose a miscompilation.
   if (!PassesToRun.empty()) {
     std::cout << "Running selected passes on program to test for crash: ";
     if (runPasses(PassesToRun))





More information about the llvm-commits mailing list