public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Priyabrata Mondal <priyabratamondal622@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>, fortran@gcc.gnu.org
Subject: Re: Request for participation in GSoC
Date: Wed, 08 Mar 2023 14:02:23 +0100	[thread overview]
Message-ID: <ri61qlzl7kw.fsf@suse.cz> (raw)
In-Reply-To: <CABcn7yjj92wn_2K67nWm0ENya9HCfWSvnuQV3EP9oygm7k-u=Q@mail.gmail.com>

Hello,

I am happy that you found contributing to GCC interesting and doubly so
that you are interested in a Fortran topic.  Let me also CC the Fortran
mailing list.

On Sat, Mar 04 2023, 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.

I assume you have read through

  https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply

have you managed to complete the steps outlined there?

If you think you need any help with any specific issue you encounter
while working through any of those, feel free to email the mailing list
again.  And David's guide is also a great resource, of course.

Good luck,

Martin

  parent reply	other threads:[~2023-03-08 13:02 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
2023-03-07 18:26   ` Priyabrata Mondal
2023-03-08 13:02 ` Martin Jambor [this message]
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=ri61qlzl7kw.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=fortran@gcc.gnu.org \
    --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).