2002-11-21 06:28:10 +08:00
|
|
|
//===- BugDriver.cpp - Top-Level BugPoint class implementation ------------===//
|
2003-10-21 01:47:21 +08:00
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file was developed by the LLVM research group and is distributed under
|
|
|
|
// the University of Illinois Open Source License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
2002-11-21 06:28:10 +08:00
|
|
|
//
|
|
|
|
// This class contains all of the shared state and information that is used by
|
|
|
|
// the BugPoint tool to track down errors in optimizations. This class is the
|
|
|
|
// main driver class that invokes all sub-functionality.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#include "BugDriver.h"
|
|
|
|
#include "llvm/Module.h"
|
2003-08-08 05:19:30 +08:00
|
|
|
#include "llvm/Pass.h"
|
2002-11-21 06:28:10 +08:00
|
|
|
#include "llvm/Assembly/Parser.h"
|
2003-08-08 05:19:30 +08:00
|
|
|
#include "llvm/Bytecode/Reader.h"
|
2002-11-21 06:28:10 +08:00
|
|
|
#include "llvm/Transforms/Utils/Linker.h"
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
#include "Support/CommandLine.h"
|
2003-08-08 05:42:28 +08:00
|
|
|
#include "Support/FileUtilities.h"
|
2002-11-21 06:28:10 +08:00
|
|
|
#include <memory>
|
|
|
|
|
2003-11-12 06:41:34 +08:00
|
|
|
using namespace llvm;
|
|
|
|
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
// Anonymous namespace to define command line options for debugging.
|
|
|
|
//
|
|
|
|
namespace {
|
|
|
|
// Output - The user can specify a file containing the expected output of the
|
|
|
|
// program. If this filename is set, it is used as the reference diff source,
|
|
|
|
// otherwise the raw input run through an interpreter is used as the reference
|
|
|
|
// source.
|
|
|
|
//
|
|
|
|
cl::opt<std::string>
|
|
|
|
OutputFile("output", cl::desc("Specify a reference program output "
|
|
|
|
"(for miscompilation detection)"));
|
|
|
|
}
|
|
|
|
|
2003-11-12 06:41:34 +08:00
|
|
|
namespace llvm {
|
|
|
|
|
2003-04-25 01:02:17 +08:00
|
|
|
/// getPassesString - Turn a list of passes into a string which indicates the
|
|
|
|
/// command line options that must be passed to add the passes.
|
|
|
|
///
|
|
|
|
std::string getPassesString(const std::vector<const PassInfo*> &Passes) {
|
|
|
|
std::string Result;
|
|
|
|
for (unsigned i = 0, e = Passes.size(); i != e; ++i) {
|
|
|
|
if (i) Result += " ";
|
|
|
|
Result += "-";
|
|
|
|
Result += Passes[i]->getPassArgument();
|
|
|
|
}
|
|
|
|
return Result;
|
|
|
|
}
|
|
|
|
|
2003-05-03 10:16:43 +08:00
|
|
|
// DeleteFunctionBody - "Remove" the function by deleting all of its basic
|
2003-04-25 06:23:34 +08:00
|
|
|
// blocks, making it external.
|
|
|
|
//
|
|
|
|
void DeleteFunctionBody(Function *F) {
|
2003-09-17 13:00:07 +08:00
|
|
|
// delete the body of the function...
|
|
|
|
F->deleteBody();
|
2003-04-25 06:23:34 +08:00
|
|
|
assert(F->isExternal() && "This didn't make the function external!");
|
|
|
|
}
|
2003-04-25 01:02:17 +08:00
|
|
|
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
BugDriver::BugDriver(const char *toolname)
|
|
|
|
: ToolName(toolname), ReferenceOutputFile(OutputFile),
|
2003-07-25 05:59:10 +08:00
|
|
|
Program(0), Interpreter(0), cbe(0), gcc(0) {}
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
|
|
|
|
|
2002-11-21 06:28:10 +08:00
|
|
|
/// ParseInputFile - Given a bytecode or assembly input filename, parse and
|
|
|
|
/// return it, or return null if not possible.
|
|
|
|
///
|
|
|
|
Module *BugDriver::ParseInputFile(const std::string &InputFilename) const {
|
|
|
|
Module *Result = 0;
|
|
|
|
try {
|
|
|
|
Result = ParseBytecodeFile(InputFilename);
|
|
|
|
if (!Result && !(Result = ParseAssemblyFile(InputFilename))){
|
|
|
|
std::cerr << ToolName << ": could not read input file '"
|
|
|
|
<< InputFilename << "'!\n";
|
|
|
|
}
|
|
|
|
} catch (const ParseException &E) {
|
|
|
|
std::cerr << ToolName << ": " << E.getMessage() << "\n";
|
|
|
|
Result = 0;
|
|
|
|
}
|
|
|
|
return Result;
|
|
|
|
}
|
|
|
|
|
|
|
|
// This method takes the specified list of LLVM input files, attempts to load
|
2003-05-23 13:34:32 +08:00
|
|
|
// them, either as assembly or bytecode, then link them together. It returns
|
|
|
|
// true on failure (if, for example, an input bytecode file could not be
|
|
|
|
// parsed), and false on success.
|
2002-11-21 06:28:10 +08:00
|
|
|
//
|
|
|
|
bool BugDriver::addSources(const std::vector<std::string> &Filenames) {
|
|
|
|
assert(Program == 0 && "Cannot call addSources multiple times!");
|
|
|
|
assert(!Filenames.empty() && "Must specify at least on input filename!");
|
|
|
|
|
|
|
|
// Load the first input file...
|
|
|
|
Program = ParseInputFile(Filenames[0]);
|
|
|
|
if (Program == 0) return true;
|
|
|
|
std::cout << "Read input file : '" << Filenames[0] << "'\n";
|
|
|
|
|
|
|
|
for (unsigned i = 1, e = Filenames.size(); i != e; ++i) {
|
|
|
|
std::auto_ptr<Module> M(ParseInputFile(Filenames[i]));
|
|
|
|
if (M.get() == 0) return true;
|
|
|
|
|
|
|
|
std::cout << "Linking in input file: '" << Filenames[i] << "'\n";
|
|
|
|
std::string ErrorMessage;
|
|
|
|
if (LinkModules(Program, M.get(), &ErrorMessage)) {
|
|
|
|
std::cerr << ToolName << ": error linking in '" << Filenames[i] << "': "
|
|
|
|
<< ErrorMessage << "\n";
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
std::cout << "*** All input ok\n";
|
|
|
|
|
|
|
|
// All input files read successfully!
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/// run - The top level method that is invoked after all of the instance
|
|
|
|
/// 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.
|
|
|
|
//
|
2003-10-14 05:04:26 +08:00
|
|
|
if (!PassesToRun.empty()) {
|
|
|
|
std::cout << "Running selected passes on program to test for crash: ";
|
|
|
|
if (runPasses(PassesToRun))
|
|
|
|
return debugCrash();
|
|
|
|
}
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
|
|
|
|
// Set up the execution environment, selecting a method to run LLVM bytecode.
|
|
|
|
if (initializeExecutionEnvironment()) return true;
|
|
|
|
|
|
|
|
// Run the raw input to see where we are coming from. If a reference output
|
|
|
|
// was specified, make sure that the raw output matches it. If not, it's a
|
|
|
|
// problem in the front-end or the code generator.
|
|
|
|
//
|
2003-08-23 02:57:43 +08:00
|
|
|
bool CreatedOutput = false;
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
if (ReferenceOutputFile.empty()) {
|
|
|
|
std::cout << "Generating reference output from raw program...";
|
2003-10-15 04:52:55 +08:00
|
|
|
ReferenceOutputFile = executeProgramWithCBE("bugpoint.reference.out");
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
CreatedOutput = true;
|
|
|
|
std::cout << "Reference output is: " << ReferenceOutputFile << "\n";
|
2003-10-15 04:52:55 +08:00
|
|
|
}
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
|
2003-10-15 04:52:55 +08:00
|
|
|
// Make sure the reference output file gets deleted on exit from this
|
|
|
|
// function, if appropriate.
|
|
|
|
struct Remover {
|
|
|
|
bool DeleteIt; const std::string &Filename;
|
|
|
|
Remover(bool deleteIt, const std::string &filename)
|
|
|
|
: DeleteIt(deleteIt), Filename(filename) {}
|
|
|
|
~Remover() {
|
|
|
|
if (DeleteIt) removeFile(Filename);
|
|
|
|
}
|
|
|
|
} RemoverInstance(CreatedOutput, ReferenceOutputFile);
|
|
|
|
|
|
|
|
// Diff the output of the raw program against the reference output. If it
|
|
|
|
// matches, then we have a miscompilation bug.
|
|
|
|
std::cout << "*** Checking the code generator...\n";
|
|
|
|
if (!diffProgram()) {
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
std::cout << "\n*** Debugging miscompilation!\n";
|
2003-10-15 04:52:55 +08:00
|
|
|
return debugMiscompilation();
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
}
|
|
|
|
|
2003-10-15 04:52:55 +08:00
|
|
|
std::cout << "\n*** Input program does not match reference diff!\n";
|
|
|
|
std::cout << "Debugging code generator problem!\n";
|
|
|
|
return debugCodeGenerator();
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
}
|
|
|
|
|
2003-10-15 04:52:55 +08:00
|
|
|
void BugDriver::PrintFunctionList(const std::vector<Function*> &Funcs) {
|
Major addition to bugpoint: ability to debug code generators (LLC and LLI).
The C backend is assumed correct and is used to generate shared objects to be
loaded by the other two code generators.
LLC debugging should be functional now, LLI needs a few more additions to work,
the major one is renaming of external functions to call the JIT lazy function
resolver.
Bugpoint now has a command-line switch -mode with options 'compile' and
'codegen' to debug appropriate portions of tools.
ExecutionDriver.cpp: Added implementations of AbstractInterpreter for LLC and
GCC, broke out common code within other tools, and added ability to generate C
code with CBE individually, without executing the program, and the GCC tool can
generate executables shared objects or executables.
If no reference output is specified to Bugpoint, it will be generated with CBE,
because it is already assumed to be correct for the purposes of debugging using
this method. As a result, many functions now accept as an optional parameter a
shared object to be loaded in, if specified.
llvm-svn: 7293
2003-07-25 02:17:43 +08:00
|
|
|
for (unsigned i = 0, e = Funcs.size(); i != e; ++i) {
|
|
|
|
if (i) std::cout << ", ";
|
|
|
|
std::cout << Funcs[i]->getName();
|
|
|
|
}
|
2003-10-16 04:42:48 +08:00
|
|
|
std::cout << std::flush;
|
2002-11-21 06:28:10 +08:00
|
|
|
}
|
2003-11-12 06:41:34 +08:00
|
|
|
|
|
|
|
} // End llvm namespace
|