We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Using LNT to track performance

Formal Metadata

Title
Using LNT to track performance
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
Last year, at the 2016 LLVM dev room, I presented ideas on how to improve LNTto make performance tracking of LLVM generated code easier. We've implementedmost 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 nowtakes about 5 to 10 minutes of work, whereas before it typically took us halfa 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 alsodiscuss how LNT is useful for other projects that need to track performance ofgenerated code. LNT is starting to be used by at least also some GCC, java jitand even a Verilog-to-C++ compiler teams. I'll also give the necessary pointers on what you need to get started on LNTfor your own projects.