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

Whitney Tsang via llvm-dev llvm-dev at lists.llvm.org
Tue Mar 24 10:43:24 PDT 2020

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
As we are mostly interested in Loop transformation passes, it would be a
good idea to also get familar with
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>

More information about the llvm-dev mailing list