[llvm-dev] [GSoC 2018] Improve Debugging of Optimized Code

[via llvm-dev]

Welcome Anastasis!  I'm very happy to see this work going forward.

I see that your first task is to make "debugify" into a function pass,
so we will be able to get data on a per-pass basis.  At EuroLLVM there
was a relevant lightning talk about a different tool, see:
http://llvm.org/devmtg/2018-04/talks.html#Lightning_11
It will be extremely interesting to see how well your results line up
with the data that Greg was able to gather on how well (or poorly)
various passes handled debug info.

I hope you have a great GSOC experience here.
--paulr

> -----Original Message-----
> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Anast
> Gramm via llvm-dev
> Sent: Wednesday, April 25, 2018 2:58 PM
> To: llvm-dev at lists.llvm.org
> Subject: [llvm-dev] [GSoC 2018] Improve Debugging of Optimized Code
> 
> Hello,
> 
> My proposal for GSoC 2018 [attachment] about
> improving debugging of optimized code was accepted.
> 
> I will work with my mentor Vedant Kumar (vsk) through the summer to
> find where DI loss occurs and try to fix as many occurrences as possible.
> 
> I will also be keeping a devlog here: https://gramanas.github.io/
> 
> You can check what the first steps of my project are on the latest post:
> https://gramanas.github.io/posts/community-bonding/
> 
> I'd love to hear any thoughts or questions you might have.
> 
> Cheers,
> Anastasis