diff options
| author | Rafael Auler <rafaelauler@fb.com> | 2024-02-06 11:18:23 -0800 |
|---|---|---|
| committer | Rafael Auler <rafaelauler@fb.com> | 2024-02-09 19:12:23 -0800 |
| commit | c1781b770d1400b62b3c324157a7895c1b9bdaaa (patch) | |
| tree | 7ad6ba005f52a88f4670d30d28cfe2018a5f7593 /bolt/lib/Passes/ValidateMemRefs.cpp | |
| parent | 2df42fe0efd92a89ae191a598e2727c7b63de80b (diff) | |
[BOLT][NFC] Refactor logging and error handlingusers/rafaelauler/bolt-logging-pr
Make core BOLT functionality more friendly to being used as a
library instead of in our standalone driver llvm-bolt. To accomplish
this, we augment BinaryContext with journaling streams that are to be
used by most BOLT code whenever something needs to be logged to the
screen. Users of the library can decide if logs should be printed to a
file, no file or to the screen, as before. To illustrate this, this
patch adds a new option --log-file that allows the user to redirect
BOLT logging to a file on disk or completely hide it by using
--log-file=/dev/null. Future BOLT code should now use
BinaryContext::outs() for printing important messages instead of
llvm::outs(). A new test log.test enforces this by verifying that no
strings are print to screen once the --log-file option is used.
We also refactor old error handling code that would directly call
exit(1) inside BOLT libraries whenever a serious problem occurred. To
overcome this, we add a new class BOLTError and auxiliary functions
createFatalBOLTError() and createNonFatalBOLTError() that allows BOLT
libs to bubble up the problem to the caller by using the Error class
as a return type (or Expected). To easily handle problems as before
(by quitting with exit(1)), callers can now use
BinaryContext::logBOLTErrorsAndQuitOnFatal(Error) whenever code needs
to deal with BOLT errors. To test this, we have fatal.s that checks
we are correctly quitting and printing a fatal error to the screen.
Because this is a significant change by itself, not all code was yet
ported. Code from Profiler libs (DataAggregator and friends) still
print errors directly to screen.
Diffstat (limited to 'bolt/lib/Passes/ValidateMemRefs.cpp')
| -rw-r--r-- | bolt/lib/Passes/ValidateMemRefs.cpp | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/bolt/lib/Passes/ValidateMemRefs.cpp b/bolt/lib/Passes/ValidateMemRefs.cpp index 3324776830d1..f29a97c43f49 100644 --- a/bolt/lib/Passes/ValidateMemRefs.cpp +++ b/bolt/lib/Passes/ValidateMemRefs.cpp @@ -72,13 +72,13 @@ void ValidateMemRefs::runOnFunction(BinaryFunction &BF) { } } -void ValidateMemRefs::runOnFunctions(BinaryContext &BC) { +Error ValidateMemRefs::runOnFunctions(BinaryContext &BC) { if (!BC.isX86()) - return; + return Error::success(); // Skip validation if not moving JT if (opts::JumpTables == JTS_NONE || opts::JumpTables == JTS_BASIC) - return; + return Error::success(); ParallelUtilities::WorkFuncWithAllocTy ProcessFunction = [&](BinaryFunction &BF, MCPlusBuilder::AllocatorIdTy AllocId) { @@ -94,10 +94,11 @@ void ValidateMemRefs::runOnFunctions(BinaryContext &BC) { LLVM_DEBUG(dbgs() << "BOLT-DEBUG: memrefs validation is concluded\n"); if (!ReplacedReferences) - return; + return Error::success(); - outs() << "BOLT-INFO: validate-mem-refs updated " << ReplacedReferences - << " object references\n"; + BC.outs() << "BOLT-INFO: validate-mem-refs updated " << ReplacedReferences + << " object references\n"; + return Error::success(); } } // namespace llvm::bolt |
