Skip to content

Commit 6b5bde6

Browse files
authored
[analyzer] Refine TimeTrace name for dispatchWorkItem (#128352)
Fixes #125508 (comment)
1 parent 11fdead commit 6b5bde6

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

clang/lib/StaticAnalyzer/Core/CoreEngine.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ bool CoreEngine::ExecuteWorkList(const LocationContext *L, unsigned MaxSteps,
183183

184184
static std::string timeTraceScopeName(const ProgramPoint &Loc) {
185185
if (llvm::timeTraceProfilerEnabled()) {
186-
return llvm::formatv("Loc {0}",
186+
return llvm::formatv("dispatchWorkItem {0}",
187187
ProgramPoint::getProgramPointKindName(Loc.getKind()))
188188
.str();
189189
}

clang/test/Analysis/ftime-trace.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
// The trace also contains durations of each step, but they are so short that they are not reliably present
2424
// in each run. However, they are also aggregated into Total *, for example:
2525
//
26-
// CHECK: "name": "Total Loc PostStmt",
26+
// CHECK: "name": "Total dispatchWorkItem PostStmt",
2727
// CHECK-NEXT: "args": {
2828
// CHECK-NEXT: "count": {{[0-9]+}},
2929
// CHECK-NEXT: "avg ms": {{[0-9]+}}

0 commit comments

Comments
 (0)