[lldb] Abstract scoped timer logic behind LLDB_SCOPED_TIMER (NFC)
This patch introduces a LLDB_SCOPED_TIMER macro to hide the needlessly repetitive creation of scoped timers in LLDB. It's similar to the LLDB_LOG(F) macro. Differential revision: https://reviews.llvm.org/D93663
This commit is contained in:
@@ -1001,8 +1001,7 @@ bool ScriptInterpreterPythonImpl::ExecuteOneLine(
|
||||
}
|
||||
|
||||
void ScriptInterpreterPythonImpl::ExecuteInterpreterLoop() {
|
||||
static Timer::Category func_cat(LLVM_PRETTY_FUNCTION);
|
||||
Timer scoped_timer(func_cat, LLVM_PRETTY_FUNCTION);
|
||||
LLDB_SCOPED_TIMER();
|
||||
|
||||
Debugger &debugger = m_debugger;
|
||||
|
||||
@@ -2220,8 +2219,7 @@ bool ScriptInterpreterPythonImpl::GetScriptedSummary(
|
||||
StructuredData::ObjectSP &callee_wrapper_sp,
|
||||
const TypeSummaryOptions &options, std::string &retval) {
|
||||
|
||||
static Timer::Category func_cat(LLVM_PRETTY_FUNCTION);
|
||||
Timer scoped_timer(func_cat, LLVM_PRETTY_FUNCTION);
|
||||
LLDB_SCOPED_TIMER();
|
||||
|
||||
if (!valobj.get()) {
|
||||
retval.assign("<no object>");
|
||||
@@ -3240,8 +3238,7 @@ void ScriptInterpreterPythonImpl::InitializePrivate() {
|
||||
|
||||
g_initialized = true;
|
||||
|
||||
static Timer::Category func_cat(LLVM_PRETTY_FUNCTION);
|
||||
Timer scoped_timer(func_cat, LLVM_PRETTY_FUNCTION);
|
||||
LLDB_SCOPED_TIMER();
|
||||
|
||||
// RAII-based initialization which correctly handles multiple-initialization,
|
||||
// version- specific differences among Python 2 and Python 3, and saving and
|
||||
|
||||
Reference in New Issue
Block a user