public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Madhu patel <patelmadhu06@gmail.com>
To: gcc@gcc.gnu.org, "hubicka@ucw.cz" <hubicka@ucw.cz>
Subject: GSoC'2023: Bypass assembler when generating LTO object files: GCC
Date: Thu, 9 Mar 2023 01:27:01 +0530	[thread overview]
Message-ID: <CABDzTvayY5ExKUFuMa8sJhh_5-7m=z_iRoaXTgR3q6QfY3k1tw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

Hi Jan,

I'm interested in working on the project `Bypass assembler when generating
LTO object files` in the GCC organization through GSoC'2023.

I am Madhu Patel, a fourth-year B.Tech. student in Computer Science at
IGDTUW, with a CGPA of 8.7/10. I have previously interned at Adobe India,
Rabvik Innovations, and FM solutions, and I am currently a research intern
at IIT Roorkee. I am also working on a research paper on Linux Kernel
Evolution for the USENIX publication. Moreover, my research paper on Stock
Price Prediction was recently accepted at the IEEE Conference. You can find
more information about my work on my LinkedIn and GitHub profiles.

Please suggest a few initial tasks I can work on during the application
period and attach them to my application. I have already prepared a
timeline/planner, great if you could have a look at it and suggest any
enhancements. Additionally, I have signed in to the mailing lists, and IRCs
and done the initial tasks as described on the project page [1]
<https://gcc.gnu.org/wiki/SummerOfCode>.

Thanks,
Madhu Patel
LinkedIn <https://www.linkedin.com/in/madhu-patel/> | Github
<https://github.com/Madhupatel08>

             reply	other threads:[~2023-03-08 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 19:57 Madhu patel [this message]
2023-03-14 17:18 ` Martin Jambor
     [not found]   ` <CABDzTva2fqqVLEPC7U7CbJJ11rHDDcKLjzPGPxFQXwXG+djHgA@mail.gmail.com>
2023-03-21 20:08     ` Martin Jambor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABDzTvayY5ExKUFuMa8sJhh_5-7m=z_iRoaXTgR3q6QfY3k1tw@mail.gmail.com' \
    --to=patelmadhu06@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).