public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rishi Raj <rishiraj45035@gmail.com>
To: gcc@gcc.gnu.org
Subject: [GSOC] Looking for small patch/project to work on
Date: Sat, 4 Mar 2023 08:11:04 +0530	[thread overview]
Message-ID: <CA+1a67OTLwfiQpmyvmJabbGQPbyNSq6qsZJTmFoFi=jZPDa0-A@mail.gmail.com> (raw)

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

Hi everyone,

My name is Rishi Raj, and I am a third-year undergraduate studying Computer
Science and Engineering at the Indian Institute of Technology Kharagpur in
India. I wish to participate in this year's GSOC with GCC.

My progress so far:

   1. Successfully built the GCC from source using the installing gcc
   guide. (I will run the test suite today.)
   2. Read about different configuration options during installations and
   also went through the gcc-newbies-guide, which was an exciting read and
   provided an overview of how to proceed in gcc-contribution. I want to
   extend my appreciation to David for this.

After reading about the suggested projects described on GCC's GSOC page, I
found "Bypass assembler when generating LTO object files" and "C++:
Implement compiler built-in traits for the standard library traits"
interesting. Currently, I am examining the preliminary patch
https://gcc.gnu.org/ml/gcc/2014-09/msg00340.html for the first project. I
can work on a small project/patch after this in a day or two. I would
greatly appreciate your suggestions for the same.

I have taken compiler theory and laboratory courses as a part of my
institute curriculum. In the laboratory, we designed a tiny-c compiler (a
subset of GCC). In theory, I learned about different phases of
compilations, various optimization techniques, etc.

Please find my course website link for a detailed overview:
https://cse.iitkgp.ac.in/~bivasm/compiler2022.html#Lecture

This course was the starting point of my interest in compiler development,
and I want to take it further by making meaningful contributions to GCC. I
hope to make some significant contributions to GCC this summer and in the
future. I would appreciate any suggestions on taking on a small
patch/project or delving deeper into the projects I am interested in
pursuing.


Best regards,

Rishi Raj

             reply	other threads:[~2023-03-04  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04  2:41 Rishi Raj [this message]
2023-03-06 16:25 ` David Malcolm
2023-03-08 12:52 ` 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='CA+1a67OTLwfiQpmyvmJabbGQPbyNSq6qsZJTmFoFi=jZPDa0-A@mail.gmail.com' \
    --to=rishiraj45035@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).