2002-12-23 23:50:16 +00:00
|
|
|
//===- ExecutionDriver.cpp - Allow execution of LLVM program --------------===//
|
2003-10-20 17:47:21 +00: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-12-23 23:50:16 +00:00
|
|
|
//
|
|
|
|
// This file contains code used to execute the program utilizing one of the
|
|
|
|
// various ways of running LLVM bytecode.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
/*
|
|
|
|
BUGPOINT NOTES:
|
|
|
|
|
|
|
|
1. Bugpoint should not leave any files behind if the program works properly
|
|
|
|
2. There should be an option to specify the program name, which specifies a
|
|
|
|
unique string to put into output files. This allows operation in the
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
SingleSource directory, e.g. default to the first input filename.
|
2002-12-23 23:50:16 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include "BugDriver.h"
|
|
|
|
#include "Support/CommandLine.h"
|
2003-08-01 22:13:59 +00:00
|
|
|
#include "Support/Debug.h"
|
2003-08-01 20:29:45 +00:00
|
|
|
#include "Support/FileUtilities.h"
|
2003-08-07 21:19:30 +00:00
|
|
|
#include "Support/SystemUtils.h"
|
2003-10-07 13:45:51 +00:00
|
|
|
#include "llvm/Support/ToolRunner.h"
|
2002-12-23 23:50:16 +00:00
|
|
|
#include <fstream>
|
2002-12-24 00:44:34 +00:00
|
|
|
#include <iostream>
|
2003-11-11 22:41:34 +00:00
|
|
|
using namespace llvm;
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
namespace {
|
|
|
|
// OutputType - Allow the user to specify the way code should be run, to test
|
|
|
|
// for miscompilation.
|
|
|
|
//
|
|
|
|
enum OutputType {
|
2003-10-21 17:41:35 +00:00
|
|
|
AutoPick, RunLLI, RunJIT, RunLLC, RunCBE
|
2002-12-23 23:50:16 +00:00
|
|
|
};
|
2003-09-29 22:40:52 +00:00
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
cl::opt<OutputType>
|
|
|
|
InterpreterSel(cl::desc("Specify how LLVM code should be executed:"),
|
2003-10-21 17:41:35 +00:00
|
|
|
cl::values(clEnumValN(AutoPick, "auto", "Use best guess"),
|
|
|
|
clEnumValN(RunLLI, "run-int", "Execute with the interpreter"),
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
clEnumValN(RunJIT, "run-jit", "Execute with JIT"),
|
|
|
|
clEnumValN(RunLLC, "run-llc", "Compile with LLC"),
|
|
|
|
clEnumValN(RunCBE, "run-cbe", "Compile with CBE"),
|
2003-10-18 20:18:20 +00:00
|
|
|
0),
|
2003-10-21 17:41:35 +00:00
|
|
|
cl::init(AutoPick));
|
2003-04-23 20:31:37 +00:00
|
|
|
|
2004-02-11 18:37:32 +00:00
|
|
|
cl::opt<bool>
|
|
|
|
CheckProgramExitCode("check-exit-code",
|
|
|
|
cl::desc("Assume nonzero exit code is failure (default on)"),
|
|
|
|
cl::init(true));
|
|
|
|
|
2003-04-23 20:31:37 +00:00
|
|
|
cl::opt<std::string>
|
|
|
|
InputFile("input", cl::init("/dev/null"),
|
|
|
|
cl::desc("Filename to pipe in as stdin (default: /dev/null)"));
|
2003-10-14 22:24:31 +00:00
|
|
|
|
|
|
|
cl::list<std::string>
|
|
|
|
AdditionalSOs("additional-so",
|
|
|
|
cl::desc("Additional shared objects to load "
|
|
|
|
"into executing programs"));
|
2002-12-23 23:50:16 +00:00
|
|
|
}
|
|
|
|
|
2003-11-11 22:41:34 +00:00
|
|
|
namespace llvm {
|
2004-01-14 03:38:37 +00:00
|
|
|
// Anything specified after the --args option are taken as arguments to the
|
|
|
|
// program being debugged.
|
|
|
|
cl::list<std::string>
|
|
|
|
InputArgv("args", cl::Positional, cl::desc("<program arguments>..."),
|
|
|
|
cl::ZeroOrMore);
|
|
|
|
}
|
2003-07-30 20:15:44 +00:00
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
// BugDriver method implementation
|
|
|
|
//
|
|
|
|
|
|
|
|
/// initializeExecutionEnvironment - This method is used to set up the
|
|
|
|
/// environment for executing LLVM programs.
|
|
|
|
///
|
|
|
|
bool BugDriver::initializeExecutionEnvironment() {
|
|
|
|
std::cout << "Initializing execution environment: ";
|
|
|
|
|
2003-09-29 22:40:52 +00:00
|
|
|
// Create an instance of the AbstractInterpreter interface as specified on
|
|
|
|
// the command line
|
2004-02-18 20:52:02 +00:00
|
|
|
cbe = 0;
|
2002-12-23 23:50:16 +00:00
|
|
|
std::string Message;
|
2003-05-03 03:19:41 +00:00
|
|
|
switch (InterpreterSel) {
|
2003-10-21 17:41:35 +00:00
|
|
|
case AutoPick:
|
|
|
|
InterpreterSel = RunCBE;
|
2004-02-18 20:52:02 +00:00
|
|
|
Interpreter = cbe = AbstractInterpreter::createCBE(getToolName(), Message);
|
2003-10-21 17:41:35 +00:00
|
|
|
if (!Interpreter) {
|
|
|
|
InterpreterSel = RunJIT;
|
|
|
|
Interpreter = AbstractInterpreter::createJIT(getToolName(), Message);
|
|
|
|
}
|
|
|
|
if (!Interpreter) {
|
|
|
|
InterpreterSel = RunLLC;
|
|
|
|
Interpreter = AbstractInterpreter::createLLC(getToolName(), Message);
|
|
|
|
}
|
|
|
|
if (!Interpreter) {
|
|
|
|
InterpreterSel = RunLLI;
|
|
|
|
Interpreter = AbstractInterpreter::createLLI(getToolName(), Message);
|
|
|
|
}
|
|
|
|
if (!Interpreter) {
|
|
|
|
InterpreterSel = AutoPick;
|
|
|
|
Message = "Sorry, I can't automatically select an interpreter!\n";
|
|
|
|
}
|
|
|
|
break;
|
2003-10-14 21:59:36 +00:00
|
|
|
case RunLLI:
|
|
|
|
Interpreter = AbstractInterpreter::createLLI(getToolName(), Message);
|
|
|
|
break;
|
|
|
|
case RunLLC:
|
|
|
|
Interpreter = AbstractInterpreter::createLLC(getToolName(), Message);
|
|
|
|
break;
|
|
|
|
case RunJIT:
|
|
|
|
Interpreter = AbstractInterpreter::createJIT(getToolName(), Message);
|
|
|
|
break;
|
|
|
|
case RunCBE:
|
2004-02-18 20:52:02 +00:00
|
|
|
Interpreter = cbe = AbstractInterpreter::createCBE(getToolName(), Message);
|
2003-10-14 21:59:36 +00:00
|
|
|
break;
|
2003-05-03 03:19:41 +00:00
|
|
|
default:
|
2003-09-29 22:40:52 +00:00
|
|
|
Message = "Sorry, this back-end is not supported by bugpoint right now!\n";
|
2003-05-03 03:19:41 +00:00
|
|
|
break;
|
2002-12-23 23:50:16 +00:00
|
|
|
}
|
2003-09-29 22:40:52 +00:00
|
|
|
std::cerr << Message;
|
2002-12-23 23:50:16 +00:00
|
|
|
|
2003-07-24 21:59:10 +00:00
|
|
|
// Initialize auxiliary tools for debugging
|
2004-02-18 20:52:02 +00:00
|
|
|
if (!cbe) {
|
|
|
|
cbe = AbstractInterpreter::createCBE(getToolName(), Message);
|
|
|
|
if (!cbe) { std::cout << Message << "\nExiting.\n"; exit(1); }
|
|
|
|
}
|
2003-10-14 21:59:36 +00:00
|
|
|
gcc = GCC::create(getToolName(), Message);
|
2003-07-24 21:59:10 +00:00
|
|
|
if (!gcc) { std::cout << Message << "\nExiting.\n"; exit(1); }
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
// If there was an error creating the selected interpreter, quit with error.
|
|
|
|
return Interpreter == 0;
|
|
|
|
}
|
|
|
|
|
2004-02-18 23:25:22 +00:00
|
|
|
/// compileProgram - Try to compile the specified module, throwing an exception
|
|
|
|
/// if an error occurs, or returning normally if not. This is used for code
|
|
|
|
/// generation crash testing.
|
|
|
|
///
|
|
|
|
void BugDriver::compileProgram(Module *M) {
|
|
|
|
// Emit the program to a bytecode file...
|
|
|
|
std::string BytecodeFile = getUniqueFilename("bugpoint-test-program.bc");
|
|
|
|
if (writeProgramToFile(BytecodeFile, M)) {
|
|
|
|
std::cerr << ToolName << ": Error emitting bytecode to file '"
|
|
|
|
<< BytecodeFile << "'!\n";
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Remove the temporary bytecode file when we are done.
|
|
|
|
FileRemover BytecodeFileRemover(BytecodeFile);
|
|
|
|
|
|
|
|
// Actually compile the program!
|
|
|
|
Interpreter->compileProgram(BytecodeFile);
|
|
|
|
}
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
|
|
|
|
/// executeProgram - This method runs "Program", capturing the output of the
|
|
|
|
/// program to a file, returning the filename of the file. A recommended
|
|
|
|
/// filename may be optionally specified.
|
|
|
|
///
|
|
|
|
std::string BugDriver::executeProgram(std::string OutputFile,
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
std::string BytecodeFile,
|
2003-10-14 21:59:36 +00:00
|
|
|
const std::string &SharedObj,
|
2004-02-11 18:37:32 +00:00
|
|
|
AbstractInterpreter *AI,
|
|
|
|
bool *ProgramExitedNonzero) {
|
2003-10-14 21:59:36 +00:00
|
|
|
if (AI == 0) AI = Interpreter;
|
|
|
|
assert(AI && "Interpreter should have been created already!");
|
2002-12-23 23:50:16 +00:00
|
|
|
bool CreatedBytecode = false;
|
|
|
|
if (BytecodeFile.empty()) {
|
|
|
|
// Emit the program to a bytecode file...
|
|
|
|
BytecodeFile = getUniqueFilename("bugpoint-test-program.bc");
|
|
|
|
|
|
|
|
if (writeProgramToFile(BytecodeFile, Program)) {
|
|
|
|
std::cerr << ToolName << ": Error emitting bytecode to file '"
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
<< BytecodeFile << "'!\n";
|
2002-12-23 23:50:16 +00:00
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
CreatedBytecode = true;
|
|
|
|
}
|
|
|
|
|
2004-02-18 22:01:21 +00:00
|
|
|
// Remove the temporary bytecode file when we are done.
|
|
|
|
FileRemover BytecodeFileRemover(BytecodeFile, CreatedBytecode);
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
if (OutputFile.empty()) OutputFile = "bugpoint-execution-output";
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
// Check to see if this is a valid output filename...
|
|
|
|
OutputFile = getUniqueFilename(OutputFile);
|
|
|
|
|
2003-10-14 21:59:36 +00:00
|
|
|
// Figure out which shared objects to run, if any.
|
2003-10-14 22:24:31 +00:00
|
|
|
std::vector<std::string> SharedObjs(AdditionalSOs);
|
2003-10-14 21:59:36 +00:00
|
|
|
if (!SharedObj.empty())
|
|
|
|
SharedObjs.push_back(SharedObj);
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
// Actually execute the program!
|
2003-10-14 21:59:36 +00:00
|
|
|
int RetVal = AI->ExecuteProgram(BytecodeFile, InputArgv, InputFile,
|
|
|
|
OutputFile, SharedObjs);
|
|
|
|
|
2004-02-11 18:37:32 +00:00
|
|
|
if (ProgramExitedNonzero != 0)
|
|
|
|
*ProgramExitedNonzero = (RetVal != 0);
|
2002-12-23 23:50:16 +00:00
|
|
|
|
|
|
|
// Return the filename we captured the output to.
|
|
|
|
return OutputFile;
|
|
|
|
}
|
|
|
|
|
2004-02-11 18:37:32 +00:00
|
|
|
/// executeProgramWithCBE - Used to create reference output with the C
|
|
|
|
/// backend, if reference output is not provided.
|
|
|
|
///
|
|
|
|
std::string BugDriver::executeProgramWithCBE(std::string OutputFile) {
|
|
|
|
bool ProgramExitedNonzero;
|
|
|
|
std::string outFN = executeProgram(OutputFile, "", "",
|
|
|
|
(AbstractInterpreter*)cbe,
|
|
|
|
&ProgramExitedNonzero);
|
|
|
|
if (ProgramExitedNonzero) {
|
|
|
|
std::cerr
|
|
|
|
<< "Warning: While generating reference output, program exited with\n"
|
|
|
|
<< "non-zero exit code. This will NOT be treated as a failure.\n";
|
|
|
|
CheckProgramExitCode = false;
|
|
|
|
}
|
|
|
|
return outFN;
|
|
|
|
}
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
|
2003-10-14 21:09:11 +00:00
|
|
|
std::string BugDriver::compileSharedObject(const std::string &BytecodeFile) {
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
assert(Interpreter && "Interpreter should have been created already!");
|
2003-10-14 21:09:11 +00:00
|
|
|
std::string OutputCFile;
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
|
|
|
|
// Using CBE
|
|
|
|
cbe->OutputC(BytecodeFile, OutputCFile);
|
|
|
|
|
|
|
|
#if 0 /* This is an alternative, as yet unimplemented */
|
|
|
|
// Using LLC
|
2003-10-14 21:09:11 +00:00
|
|
|
std::string Message;
|
2003-09-29 22:40:52 +00:00
|
|
|
LLC *llc = createLLCtool(Message);
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
if (llc->OutputAsm(BytecodeFile, OutputFile)) {
|
|
|
|
std::cerr << "Could not generate asm code with `llc', exiting.\n";
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2003-10-14 21:09:11 +00:00
|
|
|
std::string SharedObjectFile;
|
2003-10-14 21:59:36 +00:00
|
|
|
if (gcc->MakeSharedObject(OutputCFile, GCC::CFile, SharedObjectFile))
|
2003-10-14 21:09:11 +00:00
|
|
|
exit(1);
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
|
|
|
|
// Remove the intermediate C file
|
|
|
|
removeFile(OutputCFile);
|
|
|
|
|
2003-10-19 21:54:13 +00:00
|
|
|
return "./" + SharedObjectFile;
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
/// diffProgram - This method executes the specified module and diffs the output
|
|
|
|
/// against the file specified by ReferenceOutputFile. If the output is
|
|
|
|
/// different, true is returned.
|
|
|
|
///
|
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7293 91177308-0d34-0410-b5e6-96231b3b80d8
2003-07-24 18:17:43 +00:00
|
|
|
bool BugDriver::diffProgram(const std::string &BytecodeFile,
|
|
|
|
const std::string &SharedObject,
|
2003-04-24 17:02:17 +00:00
|
|
|
bool RemoveBytecode) {
|
2004-02-11 18:37:32 +00:00
|
|
|
bool ProgramExitedNonzero;
|
|
|
|
|
2002-12-23 23:50:16 +00:00
|
|
|
// Execute the program, generating an output file...
|
2004-02-11 18:37:32 +00:00
|
|
|
std::string Output = executeProgram("", BytecodeFile, SharedObject, 0,
|
|
|
|
&ProgramExitedNonzero);
|
|
|
|
|
|
|
|
// If we're checking the program exit code, assume anything nonzero is bad.
|
2004-04-02 05:33:06 +00:00
|
|
|
if (CheckProgramExitCode && ProgramExitedNonzero) {
|
|
|
|
removeFile(Output);
|
|
|
|
if (RemoveBytecode) removeFile(BytecodeFile);
|
2004-02-11 18:37:32 +00:00
|
|
|
return true;
|
2004-04-02 05:33:06 +00:00
|
|
|
}
|
2002-12-23 23:50:16 +00:00
|
|
|
|
2003-08-01 20:29:45 +00:00
|
|
|
std::string Error;
|
2002-12-23 23:50:16 +00:00
|
|
|
bool FilesDifferent = false;
|
2003-08-01 20:29:45 +00:00
|
|
|
if (DiffFiles(ReferenceOutputFile, Output, &Error)) {
|
|
|
|
if (!Error.empty()) {
|
|
|
|
std::cerr << "While diffing output: " << Error << "\n";
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
FilesDifferent = true;
|
|
|
|
}
|
2003-10-18 21:02:51 +00:00
|
|
|
|
|
|
|
// Remove the generated output.
|
|
|
|
removeFile(Output);
|
2002-12-23 23:50:16 +00:00
|
|
|
|
2003-10-18 21:02:51 +00:00
|
|
|
// Remove the bytecode file if we are supposed to.
|
2003-04-24 17:02:17 +00:00
|
|
|
if (RemoveBytecode) removeFile(BytecodeFile);
|
2002-12-23 23:50:16 +00:00
|
|
|
return FilesDifferent;
|
|
|
|
}
|
2003-07-28 19:16:14 +00:00
|
|
|
|
|
|
|
bool BugDriver::isExecutingJIT() {
|
|
|
|
return InterpreterSel == RunJIT;
|
|
|
|
}
|
2003-11-11 22:41:34 +00:00
|
|
|
|