aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
diff options
context:
space:
mode:
authorArseniy Zaostrovnykh <necto.ne@gmail.com>2025-10-20 17:25:16 +0200
committerGitHub <noreply@github.com>2025-10-20 15:25:16 +0000
commit38372df53fd7f6c8bd8c46bf720b676e12f481d9 (patch)
tree72a7251b93f69b6486d77db4b852464b88d9c76b /llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
parent77ade8905fe2102255ebb84de905f376043b68c5 (diff)
downloadllvm-38372df53fd7f6c8bd8c46bf720b676e12f481d9.zip
llvm-38372df53fd7f6c8bd8c46bf720b676e12f481d9.tar.gz
llvm-38372df53fd7f6c8bd8c46bf720b676e12f481d9.tar.bz2
[clang][analyzer] Add SyntaxRunningTime per-entry-point metric (#163341)
Per-entry-point metrics are captured during the path-sensitive analysis time. For that reason, it is not trivial to add the syntax-only analysis time as it runs in a separate stage. Luckily syntax-only analysis is done before path-senstivie analysis. I use the function summary field to keep the syntax-only anlaysis time once syntax analysis is done, and then forward it to the per-EP metrics snapshot during the path-sensitive analysis. Note that some of the entry points that were analyzed by syntax-only rules may be missing in the CSV export if they were never analyzed by path-sensitive rules. Conversely, if a function is analyzed with path-sensitive analysis but not syntax-only analysis, its `SyntaxRunningTime` will be empty. -- CPP-7099
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp')
0 files changed, 0 insertions, 0 deletions