Using LNT to track performance
Last year, at the 2016 LLVM dev room, I presented ideas on how to improve LNT to make performance tracking of LLVM generated code easier. We've implemented most ideas since, and we're happy to see that our ideas work out in practice: quite often, understanding the root cause for a performance regression now takes about 5 to 10 minutes of work, whereas before it typically took us half a day to produce all data that is now recorded automatically.
I intend to give a demo of how we use LNT at ARM's LLVM teams. I'll also discuss how LNT is useful for other projects that need to track performance of generated code. LNT is starting to be used by at least also some GCC, java jit and even a Verilog-to-C++ compiler teams.
I'll also give the necessary pointers on what you need to get started on LNT for your own projects.
You can find a preview of the kind of things I plan to demo at http://blog.llvm.org/2016/06/using-lnt-to-track-performance.html