Skip to content

[analyzer] Refine TimeTrace name for dispatchWorkItem #128352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 24, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion clang/lib/StaticAnalyzer/Core/CoreEngine.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ bool CoreEngine::ExecuteWorkList(const LocationContext *L, unsigned MaxSteps,

static std::string timeTraceScopeName(const ProgramPoint &Loc) {
if (llvm::timeTraceProfilerEnabled()) {
return llvm::formatv("Loc {0}",
return llvm::formatv("dispatchWorkItem {0}",
ProgramPoint::getProgramPointKindName(Loc.getKind()))
.str();
}
Expand Down
2 changes: 1 addition & 1 deletion clang/test/Analysis/ftime-trace.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
// The trace also contains durations of each step, but they are so short that they are not reliably present
// in each run. However, they are also aggregated into Total *, for example:
//
// CHECK: "name": "Total Loc PostStmt",
// CHECK: "name": "Total dispatchWorkItem PostStmt",
// CHECK-NEXT: "args": {
// CHECK-NEXT: "count": {{[0-9]+}},
// CHECK-NEXT: "avg ms": {{[0-9]+}}
Expand Down