public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wileam Yonatan Phan <wileamyp@outlook.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
	Bryan Carroll <carrollbryanm@gmail.com>
Cc: gcc@gcc.gnu.org, Tobias Burnus <tobias@codesourcery.com>
Subject: Re: GSoC Fortran - Do Concurrent
Date: Mon, 09 May 2022 05:44:10 -0400	[thread overview]
Message-ID: <BY5PR14MB39117FB5E0F71784F3CE986ECEC69@BY5PR14MB3911.namprd14.prod.outlook.com> (raw)
In-Reply-To: <87sfpjys2l.fsf@euler.schwinge.homeip.net>

Hi Bryan and Thomas,

That's correct, I found out about this particular GSoC project idea on DO
CONCURRENT literally within 48 hours of the contributor proposal deadline as I
outlined in my post in https://gcc.gnu.org/pipermail/gcc/2022-April/238581.html
 .

To be honest I'm excited about having GFortran to be the second compiler to be
able to offload DO CONCURRENT to the GPU after NVIDIA nvfortran. Maybe you can
even help me with the nitty-gritty stuff of, say, interfacing directly with
pthreads for the `-fdo-concurrent=parallel` backend (since I mostly use OpenMP
on the CPU side so I don't have that much experience with pthreads aside from a
graduate-level course I took on scientific computing from Prof. Jack Dongarra
at UT Knoxville).

Looking forward to collaborate on this!

Thanks,
Wil

On Mon, 2022-05-09 at 11:26 +0200, Thomas Schwinge wrote:
> Hi Bryan!
> 
> Thanks for reaching out, and welcome to GCC!
> On 2022-05-03T13:34:13-0500, Bryan Carroll via Gcc <
> gcc@gcc.gnu.org
> > wrote:
> > I know I'm too late for GSoC, but if Tobias Burnus or someone wants to
> > mentor me, I'm willing to work on the Fortran - Do Concurrent project, as a
> > volunteer, if it's not already taken. I didn't see the GSoC until a day
> > before it was due.
> 
> So did another aspirant, Wil, who within very short notice threw together
> a GSoC project application for that very task.  ;-P
> 
> I'm putting Wil in CC -- open discussion, and all that.
> 
> > A little about myself: I'm a research associate at the Center for Analysis
> > and Prediction of Storms at the National Weather Center on the University
> > of
> > Oklahoma campus. Mostly I do hardware and software support on our servers
> > and some occasional software development. I received my M.Sc. with a major
> > of Applied Mathematics and Computer Science from the University of Central
> > Oklahoma in the summer of 2020. I have experience with C, C++, Python, MPI,
> > some OpenMP, and some Fortran. I took a compiler course a few years ago; so
> > I have some experience with compilers. I've been wanting to get into GCC
> > development.
> 
> Yes, that's certainly suitable background and motivation to start
> contributing to GCC!
> 
> > If the Fortran - Do Concurrent is already taken, I'm also interested in
> > some
> > of the other projects. Let me know if you want to proceed.
> 
> We do the GSoC project ranking for GCC, but in the end it's Google who
> decide how many GSoC slots we get, etc.  So, at this point, we don't know
> yet whether Wil's "Fortran DO CONCURRENT" gets accepted as a GSoC project
> this year, or whether it possibly might not work out for other reasons.
> Assuming that Wil's GSoC project does come to fruition, we'd have to look
> for a different task for you: the GSoC rules assume that participants
> individually work on their own project.  Thus, either have to wait a bit
> longer, or find a different project that you're interested in?
> 
> 
> Grüße
>  Thomas
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
> München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
> Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht
> München, HRB 106955
> 


      reply	other threads:[~2022-05-09  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 18:34 carrollbryanm
2022-05-09  9:26 ` Thomas Schwinge
2022-05-09  9:44   ` Wileam Yonatan Phan [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=BY5PR14MB39117FB5E0F71784F3CE986ECEC69@BY5PR14MB3911.namprd14.prod.outlook.com \
    --to=wileamyp@outlook.com \
    --cc=carrollbryanm@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=thomas@codesourcery.com \
    --cc=tobias@codesourcery.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).