[llvm-dev] GSoC2019 - DebugInfo should not effect codegen

[preejackie via llvm-dev]

Hi all,

I'm interested in participating this GSoC with llvm. I would like to 
contribute on the project idea "DebugInfo should not effect codegen". 
Over the past few days, I have gone through some bugs reported at 
bugzilla that cause different codegen behavior of same program.

Bugs I have been looking at are:

     1. [fuzzDI] -O1 + `-g` cause the generated code to change. 
<https://bugs.llvm.org/show_bug.cgi?id=37306>

     2. Make llvm passes debug info invariant 
<https://bugs.llvm.org/show_bug.cgi?id=37728>

     3. LoopVectorize: different IR generation when debug info is 
present <https://bugs.llvm.org/show_bug.cgi?id=37727>

     4. InstCombine: test/Transforms/InstCombine/call-guard.ll looks 
different with debug info present 
<https://bugs.llvm.org/show_bug.cgi?id=37714>

I'm currently working on finding the root cause of these issues. I have 
some questions regarding the scope of the project.

    1) Whether the scope is finding as many issue as possible and fix it or whether I can design some protocol like stuff which impose constrains on optimization passes to interact with debug
       info metadata, by this way we can far more generalize this idea and make a clear distinction between opt passes which operate on llvm ir & debug metadata.

I highly appreciate your thoughts on it.
Thanks

-- 
Have a great day!
PreeJackie

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