I hate it when bugpoint is all ready to give me a bytecode file, then crashes

in final cleanups.  Then you had to run the whole mess again with
-disable-final-cleanups.

This makes bugpoint run the cleanups in a protected environment so that if
they crash, bugpoint itself doesn't crash.  This makes things much happier,
implements a FIXME, and gets rid of YABPO (yet another bugpoint option).


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9743 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 2 insertions, 2 deletions

diff --git a/tools/bugpoint/BugDriver.h b/tools/bugpoint/BugDriver.h
index 6c48c04..e1af721 100644
--- a/tools/bugpoint/BugDriver.h
+++ b/tools/bugpoint/BugDriver.h
@@ -120,7 +120,7 @@ private:
 
 
   /// EmitProgressBytecode - This function is used to output the current Program
-  /// to a file named "bugpoing-ID.bc".
+  /// to a file named "bugpoint-ID.bc".
   ///
   void EmitProgressBytecode(const std::string &ID, bool NoFlyer = false);
   
@@ -162,7 +162,7 @@ private:
   /// the MayModifySemantics argument is true, then the cleanups is allowed to
   /// modify how the code behaves.
   ///
-  void performFinalCleanups(Module *M, bool MayModifySemantics = false) const;
+  Module *performFinalCleanups(Module *M, bool MayModifySemantics = false);
 
   /// initializeExecutionEnvironment - This method is used to set up the
   /// environment for executing LLVM programs.