[PATCH] D65585: WIP: [llvm-locstats] Add the llvm-locstats tool
Adrian Prantl via llvm-commits
llvm-commits at lists.llvm.org
Mon Aug 5 09:49:50 PDT 2019
> On Aug 2, 2019, at 6:10 PM, vsk at apple.com wrote:
>
> Hi Djordje,
>
> I take your point about not wanting to clutter up llvm-dwarfdump --statistics output.
>
> I'll note that, beyond code sharing, there are significant benefits to emitting all `locstats` information using the existing `--statistics` option:
>
> 1) We can check in a simple script in utils/ to pretty-print the `--statistics` JSON output, such that we get exactly what is emitted by the `locstats` tool today.
>
> 2) Emitting stats in JSON is great for continuous integration jobs that track debug info quality over time. It'd be great to include the metrics reported by `locstats` in these jobs.
And I should point out that this is not a hypothetical scenario. This job:
http://green.lab.llvm.org/green/view/LLDB/job/clang-3.4-debuginfo-statistics/ <http://green.lab.llvm.org/green/view/LLDB/job/clang-3.4-debuginfo-statistics/>
Pushes data into:
http://lnt.llvm.org/db_default/v4/nts/machine/1357 <http://lnt.llvm.org/db_default/v4/nts/machine/1357>
which generates graphs like:
http://lnt.llvm.org/db_default/v4/nts/graph?plot.0=1357.1607043.4&highlight_run=127815 <http://lnt.llvm.org/db_default/v4/nts/graph?plot.0=1357.1607043.4&highlight_run=127815>
several times per hour. Any new JSON fields show up there without any extra manual intervention.
-- adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20190805/31773467/attachment.html>
More information about the llvm-commits
mailing list