llvm dev - Mar 2021 - [GSoC] Prospective student for Fix fundamental issues in LLVM's IR

Hello,

I am an undergrad from India. This summer, I'm interested in working on
fixing the fundamental issues in LLVM's IR. I have a moderate understanding
of LLVM IR. I also did my Google Summer of Code 2020 with LLVM, where I
worked on unifying code motion checks present in loop transformation and
analysis passes. (Phabricator
<https://summerofcode.withgoogle.com/archive/2020/projects/5488234206855168/>)
(GSoC archive
<https://summerofcode.withgoogle.com/archive/2020/projects/5488234206855168/>
)


I followed some previous messages about the project and found some
resources to read. I visited alive2's dashboard and found that I worked
with these passes during my previous GSoC and have a good understanding of
these passes.


I also read the paper and followed the slides. The paper closely describes
the need for making changes in the LLVM IR, and it also describes few
techniques to achieve the goal. Introducing poison, freeze, and more
methods to weaken the undefined behavior sounds exciting and required in
the LLVM IR.


I looked at the bug logs (link
<https://web.ist.utl.pt/nuno.lopes/alive2/index.php?hash=a608503f5881d583>)
of alive2, and I found that in a few passes, the reason for failure is the
same (maybe different conditions but same reason). I am thinking of
grouping all similar bugs and targeting the bugs in groups. I believe that
the same type of error will trigger similar or related semantics fixtures.


I also watched your talks at PLDI 2017, 2016 LLVM developers' meeting, and
2020 LLVM developers' meeting and enjoyed all the talks. I also want to
congratulate Nuno and Juneyoung on their paper getting selected in PLDI'21.
I will be joining the conference as a student volunteer.


I liked the whole idea, and it looks pretty rational and exciting to me.
I'll start drafting the proposal after your initial feedback/suggestions.
I'm really very excited to work on this.

Best regards,

Rithik Sharma
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20210327/e4a63877/attachment-0001.html>

Hi Rithik,

Thanks for your interest. Please have a look at my previous reply:
https://lists.llvm.org/pipermail/llvm-dev/2021-March/149063.html

Looking forward to read your proposal. Let me know if you have questions in the
meantime.

Nuno

_____________________________________________
From: Rithik Sharma <rithiksh02 at gmail.com> 
Sent: 27 March 2021 18:03
Subject: [GSoC] Prospective student for Fix fundamental issues in LLVM's IR

Hello,


I am an undergrad from India. This summer, I'm interested in working on
fixing the fundamental issues in LLVM's IR. I have a moderate understanding
of LLVM IR. I also did my Google Summer of Code 2020 with LLVM, where I worked
on unifying code motion checks present in loop transformation and analysis
passes.
(https://summerofcode.withgoogle.com/archive/2020/projects/5488234206855168/)
(https://summerofcode.withgoogle.com/archive/2020/projects/5488234206855168/)

I followed some previous messages about the project and found some resources to
read. I visited alive2's dashboard and found that I worked with these passes
during my previous GSoC and have a good understanding of these passes.

I also read the paper and followed the slides. The paper closely describes the
need for making changes in the LLVM IR, and it also describes few techniques to
achieve the goal. Introducing poison, freeze, and more methods to weaken the
undefined behavior sounds exciting and required in the LLVM IR.

I looked at the bug logs
(https://web.ist.utl.pt/nuno.lopes/alive2/index.php?hash=a608503f5881d583) of
alive2, and I found that in a few passes, the reason for failure is the same
(maybe different conditions but same reason). I am thinking of grouping all
similar bugs and targeting the bugs in groups. I believe that the same type of
error will trigger similar or related semantics fixtures.

I also watched your talks at PLDI 2017, 2016 LLVM developers' meeting, and
2020 LLVM developers' meeting and enjoyed all the talks. I also want to
congratulate Nuno and Juneyoung on their paper getting selected in PLDI'21.
I will be joining the conference as a student volunteer.

I liked the whole idea, and it looks pretty rational and exciting to me.
I'll start drafting the proposal after your initial feedback/suggestions.
I'm really very excited to work on this.
Best regards,
Rithik Sharma