public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gaurang Aswal <gaurangaswal2408@gmail.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
	Gfortran mailing list <fortran@gcc.gnu.org>
Subject: Re: GSoc Topics
Date: Wed, 24 Jan 2024 11:28:40 +0530	[thread overview]
Message-ID: <CANYmVHtyQR_G3yoed+ZYNf3dMsJMPkYUXwkS-m6nP6pZcLajMg@mail.gmail.com> (raw)
In-Reply-To: <65b03c3a.500a0220.6ecb2.84dbSMTPIN_ADDED_BROKEN@mx.google.com>

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

Thanks, I'll check them out.

On Wed, 24 Jan, 2024, 03:52 Martin Jambor, <mjambor@suse.cz> wrote:

> Hello,
>
> We are delighted you found contributing to GCC interesting.  GCC has
> applied to be part of GSoC 2024 but of course selected organizations
> have not been announced yet.
>
> On Fri, Jan 12 2024, Gaurang Aswal via Gcc wrote:
> > Hey I am Gaurang Aswal a 4th year B.E. Computer Science student from BITS
> > Goa, India and wanted some info and insights on the Fortran projects and
> I
> > am interested in working on them.
>
> While the list of suggested projects at
> https://gcc.gnu.org/wiki/SummerOfCode is undergoing review for 2024, I
> think the Fortran ones will not change much.  Please look over them, try
> to figure out what they would entail and which you'd like best.  In this
> reply I have also CCed the Fortran mailing list, people there might help
> you decide which Fortan project would be the best for you.
>
>
> > I have basic knowledge of C/C++ and I
> > have completed my basic computer science courses in the same language,
> > which included Object Oriented Programming, Data Structures and
> Algorithms,
> > Computer Architecture and Operating Systems. I would like to keep in
> touch
> > and want to know how to proceed working on the topics.
>
> Contributing to the compiler also requires some rudimentary theoretical
> background in compilers, at the very least understanding of the concept
> of Intermediate Representation (IR), often also called Intermediate
> Language (IL).  Googling either of the two terms should help you to find
> a lot of material to familiarize yourself with it.
>
> Please also look again at the "Before you apply" section of the idea
> page https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply and make
> sure you are able to build, install and test GCC and then have it
> generate dumps and step through some function during compilation.
>
> Also, feel free to ask for help here with any specific GCC development
> issues you may encounter.
>
> Good luck,
>
> Martin
>

      parent reply	other threads:[~2024-01-24  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 16:55 Gaurang Aswal
2024-01-23 22:22 ` Martin Jambor
     [not found] ` <65b03c3a.500a0220.6ecb2.84dbSMTPIN_ADDED_BROKEN@mx.google.com>
2024-01-24  5:58   ` Gaurang Aswal [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=CANYmVHtyQR_G3yoed+ZYNf3dMsJMPkYUXwkS-m6nP6pZcLajMg@mail.gmail.com \
    --to=gaurangaswal2408@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.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).