public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Priyabrata Mondal <priyabratamondal622@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Request for participation in GSoC
Date: Mon, 06 Mar 2023 11:29:28 -0500	[thread overview]
Message-ID: <4c5144f6fe2b94644f20d91423a58d13055a6b16.camel@redhat.com> (raw)
In-Reply-To: <CABcn7yjj92wn_2K67nWm0ENya9HCfWSvnuQV3EP9oygm7k-u=Q@mail.gmail.com>

On Sat, 2023-03-04 at 20:56 +0530, Priyabrata Mondal via Gcc wrote:
>   Respected sir,
>            I am Priyabrata Mondal, an M.tech student in Electric
> Transportation at the Indian Institute of Technology(IIT), Mandi. I
> want to
> participate in Google Summer of Code 2023 by contributing to the
> *Fortran –
> DO CONCURRENT* project, an implementation of loop that executes
> concurrently. I have started to learn about parallel programming and
> Fortran programming language.
>              I have good knowledge of C, C++, Javascript, HTML, and
> CSS.
>             can you suggest some resources so I can learn the
> technologies
> that are required for this project?
>              I will be highly grateful to you forever if you allow me
> to do
> this project under your guidance.

Hello, welcome to the GCC community.

If you haven't seen it already, I've written a guide aimed at new GCC
developers here:
  https://gcc-newbies-guide.readthedocs.io/en/latest/index.html

A good first step would be to try to build gcc from source, add a
simple warning that emits:
  "hello world, I'm compiling function 'foo'"
for each function being compiled, and compile something with that...
and then do that again, stepping through it in the debugger.  There are
instructions about that in the guide above.

Hope this is helpful
Dave


  reply	other threads:[~2023-03-06 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 15:26 Priyabrata Mondal
2023-03-06 16:29 ` David Malcolm [this message]
2023-03-07 18:26   ` Priyabrata Mondal
2023-03-08 13:02 ` Martin Jambor
2023-03-08 13:28   ` Tobias Burnus

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=4c5144f6fe2b94644f20d91423a58d13055a6b16.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=priyabratamondal622@gmail.com \
    /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).