From: Aditya Ballaki <adi.ballaki@gmail.com>
To: gcc@gcc.gnu.org
Subject: GSoC 2024 Expression of interes
Date: Wed, 28 Feb 2024 04:41:52 +0800 [thread overview]
Message-ID: <CALPwvW3t0fw4oxeUOgvTsnbGOU7Nq3Wk_OeEf9SxM3sW1go-aQ@mail.gmail.com> (raw)
Hi Team,
I'm an incoming graduate student in Computer Engineering at Cornell
University, and I'm keen on participating in GSOC by contributing to
open-source projects before starting my graduate program.
Specifically, I'm interested in working on the Rust GCC compiler.
While I haven't made direct open-source contributions before, I'm
quite familiar with Rust. I've also gained experience with C/C++
through various projects involving low-level hardware programming and
video game development. Moreover, I've worked with several other tech
stacks and production-level code during my internships and research
endeavours.
Please let me know if it's appropriate for me to reach out to any of
the listed mentors (Pierre-Emmanuel Patry, Philip Herron, Arthur
Cohen) to discuss the project further.
Thank you!
Regards,
Aditya
P.S: Re-sent email with the correct string 'GSoC' in the subject line
next reply other threads:[~2024-02-27 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 20:41 Aditya Ballaki [this message]
2024-03-01 15:59 ` 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=CALPwvW3t0fw4oxeUOgvTsnbGOU7Nq3Wk_OeEf9SxM3sW1go-aQ@mail.gmail.com \
--to=adi.ballaki@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).