llvm dev - Mar 2020 - [GSoC] Prospective student for Unify ways to move code or check if code is safe to be moved

Hello,

I am an undergrad from India. This summer I'm interested in working on
unifying the code motion checks as a GSoC intern with LLVM. I started
reading about classical data flow analysis since few months, I see this as
a great opportunity to start contributing to LLVM. The idea of unifying all
the code motion checks into one place seems very rational and interesting
to me. As in the project description LICM was mentioned, I have a basic
idea about it and I spent some time to go through its implementation in
LLVM. It makes a lot of sense to me to keep all code motion checks at one
place, say an analysis pass, I also looked into GVN hoist & sink passes as
they also have some code motion logic. 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/20200322/9167f1fd/attachment.html>

Ping!
I'm bit concern about the approaching deadline next week, some pointers
will be really appreciated and will be very helpful to me.

Best regards,
Rithik Sharma

On Sun, 22 Mar 2020 at 01:24, RITHIK SHARMA <rithiksh02 at gmail.com>
wrote:
> Hello,
>
> I am an undergrad from India. This summer I'm interested in working on
> unifying the code motion checks as a GSoC intern with LLVM. I started
> reading about classical data flow analysis since few months, I see this as
> a great opportunity to start contributing to LLVM. The idea of unifying all
> the code motion checks into one place seems very rational and interesting
> to me. As in the project description LICM was mentioned, I have a basic
> idea about it and I spent some time to go through its implementation in
> LLVM. It makes a lot of sense to me to keep all code motion checks at one
> place, say an analysis pass, I also looked into GVN hoist & sink passes
as
> they also have some code motion logic. 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/20200324/6937ac49/attachment.html>

Hi Rithik,

I CC'd the 2 other mentors and hopefully you'll get answer. Sorry, but I
don't know of any other way to help. :/
You may also try to contact them privately.

Best,
Stefanos


Στις Τρί, 24 Μαρ 2020 στις 7:35 μ.μ., ο/η RITHIK SHARMA via llvm-dev <
llvm-dev at lists.llvm.org> έγραψε:
> Ping!
> I'm bit concern about the approaching deadline next week, some pointers
> will be really appreciated and will be very helpful to me.
>
> Best regards,
> Rithik Sharma
>
> On Sun, 22 Mar 2020 at 01:24, RITHIK SHARMA <rithiksh02 at gmail.com>
wrote:
>
>> Hello,
>>
>> I am an undergrad from India. This summer I'm interested in working
on
>> unifying the code motion checks as a GSoC intern with LLVM. I started
>> reading about classical data flow analysis since few months, I see this
as
>> a great opportunity to start contributing to LLVM. The idea of unifying
all
>> the code motion checks into one place seems very rational and
interesting
>> to me. As in the project description LICM was mentioned, I have a basic
>> idea about it and I spent some time to go through its implementation in
>> LLVM. It makes a lot of sense to me to keep all code motion checks at
one
>> place, say an analysis pass, I also looked into GVN hoist & sink
passes as
>> they also have some code motion logic. I'll start drafting the
proposal
>> after your initial feedback/suggestions. I'm really very excited to
work on
>> this.
>>
>> Best Regards,
>> Rithik Sharma
>>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200324/9b0f1538/attachment.html>

Accidentally not reply all.
Just as a record:
Hi Rithik,

Thanks for your interest. I can see that you are at the right direction.
Another useful area to look at is the CodeMoverUtils in
https://github.com/llvm/llvm-project/blob/master/llvm/include/llvm/Transforms/Utils/CodeMoverUtils.h
 .
As we are mostly interested in Loop transformation passes, it would be a
good idea to also get familar with
https://llvm.org/doxygen/classllvm_1_1Loop.html.
Identify the different code motion checks in different loop passes and
identifying the differences in them to categorize them and later implement
them in CodeMoverUtils.

Good luck,
Whitney Tsang

On Tue, Mar 24, 2020 at 12:34 PM RITHIK SHARMA <rithiksh02 at gmail.com>
wrote:
> Ping!
> I'm bit concern about the approaching deadline next week, some pointers
> will be really appreciated and will be very helpful to me.
>
> Best regards,
> Rithik Sharma
>
> On Sun, 22 Mar 2020 at 01:24, RITHIK SHARMA <rithiksh02 at gmail.com>
wrote:
>
>> Hello,
>>
>> I am an undergrad from India. This summer I'm interested in working
on
>> unifying the code motion checks as a GSoC intern with LLVM. I started
>> reading about classical data flow analysis since few months, I see this
as
>> a great opportunity to start contributing to LLVM. The idea of unifying
all
>> the code motion checks into one place seems very rational and
interesting
>> to me. As in the project description LICM was mentioned, I have a basic
>> idea about it and I spent some time to go through its implementation in
>> LLVM. It makes a lot of sense to me to keep all code motion checks at
one
>> place, say an analysis pass, I also looked into GVN hoist & sink
passes as
>> they also have some code motion logic. 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/20200324/27a1e2f4/attachment.html>