public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@schwinge.name>
To: Arpit Gupta <cs21b062@iittp.ac.in>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: GSoC: Application for Rust Front-End Project at GCC
Date: Fri, 12 Jan 2024 12:13:53 +0100	[thread overview]
Message-ID: <87v87yn6ry.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <CACZVFowRH9XQ-krXroCNd+V7UqDgr=7_+Y1NfaE3tZE_+T8pOg@mail.gmail.com>

Hi Arpit!

On 2024-01-11T08:15:28+0530, CS21B062 ARPIT GUPTA <cs21b062@iittp.ac.in> wrote:
> Thank you for your email. But is there anyway I can start contributing. I
> have worked upon similar ground before, and as such I am looking for a
> summer undergrad internship. I wanted to build my profile by doing open
> source contribution.

Yes, sure, you may contribute to GCC anytime!  (..., and then later do a
GSoC project, too, of course.)

For GCC/Rust specifically, please have a look at
<https://rust-gcc.github.io/>.  In particular, newcomers seem to find it
helpful to join Zulip, and introduce themselves there, and get started on
a first small task.


Grüße
 Thomas


> On Thu, 11 Jan, 2024, 4:16 am Thomas Schwinge, <thomas@schwinge.name> wrote:
>
>> Hi Arpit!
>>
>> First, welcome to GCC, and I appreciate your enthousiasm!
>>
>> On 2023-12-30T22:30:37+0530, CS21B062 ARPIT GUPTA <cs21b062@iittp.ac.in>
>> wrote:
>> > Dear GCC Community,
>> >
>> > I hope this email finds you well. My name is Arpit and I am writing to
>> > express my interest in participating in GSoC, specifically for the
>> > Rust Front-End project at GCC.
>>
>> You're, however, too late for GSoC 2023 (..., which you'd referenced at
>> the end of your email), but also still too early for GSoC 2024; see
>> <https://developers.google.com/open-source/gsoc/timeline>.
>>
>> Building the compiler and beginning to experiment as well as reaching out
>> to the community is always a good start, so if you're interested in
>> GCC/Rust specifically, please have a look at
>> <https://rust-gcc.github.io/>.
>>
>>
>> Grüße
>>  Thomas
>>
>>
>> > Having completed an internship in
>> > Compiler Design at IIT Hyderabad in my IInd Year , where I gained
>> > hands-on experience in code compliance, optimization analysis, and
>> > cross-compilation, I am eager to contribute to the development of the
>> > Rust compiler front-end.
>> >
>> > After carefully reviewing the available projects, I am particularly
>> > interested in the following project:
>> >
>> > Project Choice:
>> > Rust Front-End,  all the subdomains
>> >
>> > Project Description:
>> > Rust supports several metadata outputs crucial for importing crates.
>> > The goal of this project is to extend the support for metadata exports
>> > in the Rust Front-End being developed by GCC. I am confident in my
>> > understanding of compilation and linking processes, which will be
>> > essential for this project. I am excited about the opportunity to work
>> > on this challenging task and contribute to the completion of metadata
>> > exports.
>> >
>> > Why This Project:
>> > I believe that improving metadata exports is a crucial step towards
>> > enhancing the interoperability of the Rust compiler with other tools
>> > and platforms. This effort aligns with my passion for compiler design
>> > and would significantly contribute to the overall functionality of the
>> > Rust Front-End. Moreover, as an intern I have already developed some
>> > compliance checkers using clang for C language in accordance with
>> > AUTOSAR.
>> >
>> > Proposed Timeline:
>> >
>> > Weeks 1-2: In-depth analysis of the existing metadata export framework
>> > in GCC and understanding the requirements for Rust.
>> > Weeks 3-5: Implementation of basic metadata export functionality for
>> > the Rust Front-End.
>> > Weeks 6-8: Testing and debugging of the implemented features,
>> > addressing any issues that may arise during the integration.
>> > Weeks 9-12: Fine-tuning, optimization, and documentation of the
>> > metadata export process, ensuring it meets the project's goals.
>> >
>> > I am committed to engaging with the community throughout the
>> > development process, seeking feedback, and incorporating suggestions
>> > to ensure the success of the project. I have subscribed to the
>> > gcc@gcc.gnu.org mailing list and will actively participate in
>> > discussions regarding the Rust Front-End project.
>> >
>> > I would appreciate any feedback or guidance on my proposed project and
>> > timeline. I am eager to contribute to the GCC community and make a
>> > meaningful impact on the Rust Front-End project.
>> >
>> > Thank you for considering my application. I look forward to the
>> > opportunity to contribute to the GCC community during GSoC 2023.
>> >
>> > Best regards,
>> > Arpit Gupta,
>> > Code Club Head
>> > ph: 8299480636

      parent reply	other threads:[~2024-01-12 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACZVFozCvJTTToVErd9kHem_mbEaZBo2H5RjiiO15SRbUEAwJQ@mail.gmail.com>
2024-01-10 22:46 ` Thomas Schwinge
     [not found]   ` <CACZVFowRH9XQ-krXroCNd+V7UqDgr=7_+Y1NfaE3tZE_+T8pOg@mail.gmail.com>
2024-01-12 11:13     ` Thomas Schwinge [this message]

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=87v87yn6ry.fsf@euler.schwinge.homeip.net \
    --to=thomas@schwinge.name \
    --cc=cs21b062@iittp.ac.in \
    --cc=gcc-rust@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).