[LLVMdev] Recent changes in -gmlt break sample profiling (original) (raw)

Diego Novillo dnovillo at google.com
Mon Oct 27 07:46:44 PDT 2014

On Sun Oct 26 2014 at 3:47:51 PM Jeremy Lakeman <Jeremy.Lakeman at gmail.com> wrote:

This sounds like a problem best solved by tracking source code movement via your source control system. If you know the commit of the code that produced the sample, you should be able to use source control history / diffs to translate absolute line numbers to the location where the source has moved. This would have the added advantage of highlighting where those samples are likely to be useless or completely misleading.

Doable in principle, but challenging in reality. I don't think this idea is straightforward at all to implement.

Diego. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141027/2b488262/attachment.html>

More information about the llvm-dev mailing list