llvm dev - Mar 2020 - GSoC Interested Student: Make LLVM passes debug info invariant

Hello All,

I am a graduate student at Iowa State University(ISU) at Ames, IA
in the Computer Engineering department. For GSoC'20, I am interested in
working on the project "Make LLVM passes debug info variant". During
my
research work at the ISU, I have worked on Memory access monitoring of an
application using the LLVM static analysis framework, where I developed a
tool busing the LLVM module pass to perform tracing across multiple
functions using call graph analysis and also implemented static
instrumentation using LLVM APIs, to finally generate trace showing memory
accesses for a program.

In the last few days, I have looked at PR37728
<https://bugs.llvm.org/show_bug.cgi?id=37728> to learn about this meta bug
and RFC
<http://lists.llvm.org/pipermail/llvm-dev/2019-September/135433.html>   to
know the background of  known Call frame information issue in compiler
backend  to understand the motivation behind the project. If you have any
pointers related to the project that can be very useful to evaluate the
project work, please let me know.

Thanks & Regards,
Prakhar Bansal
Graduate Student' 20, Computer Engineering
Iowa State University, Ames, IA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200327/70118398/attachment.html>

Hello Prakhar,
Some additional material that you might find helpful, which is a “lightning
talk” given at an LLVM Developers Meeting in 2015 called “Verifying Code
Generation is unaffected by -g/-S”
Slides are
here<https://llvm.org/devmtg/2015-04/slides/Verifying_code_gen_dash_g_final.pdf>
and there is supposed to be video of the session but that appears to have gone
missing.
Hope this is helpful!
Best regards,
Paul Robinson

From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of PRAKHAR
BANSAL via llvm-dev
Sent: Friday, March 27, 2020 4:54 AM
To: llvm-dev <llvm-dev at lists.llvm.org>
Subject: [llvm-dev] GSoC Interested Student: Make LLVM passes debug info
invariant

Hello All,

I am a graduate student at Iowa State University(ISU) at Ames, IA in the
Computer Engineering department. For GSoC'20, I am interested in working on
the project "Make LLVM passes debug info variant". During my research
work at the ISU, I have worked on Memory access monitoring of an application
using the LLVM static analysis framework, where I developed a tool busing the
LLVM module pass to perform tracing across multiple functions using call graph
analysis and also implemented static instrumentation using LLVM APIs, to finally
generate trace showing memory accesses for a program.

In the last few days, I have looked at
PR37728<https://bugs.llvm.org/show_bug.cgi?id=37728> to learn about this
meta bug and
RFC<http://lists.llvm.org/pipermail/llvm-dev/2019-September/135433.html>  
to know the background of  known Call frame information issue in compiler
backend  to understand the motivation behind the project. If you have any
pointers related to the project that can be very useful to evaluate the project
work, please let me know.

Thanks & Regards,
Prakhar Bansal
Graduate Student' 20, Computer Engineering
Iowa State University, Ames, IA

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200327/7da62008/attachment.html>