public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jerome Huck <jeromehuck.2022@orange.fr>
Cc: gcc@gcc.gnu.org
Subject: Re: Contact Cauldron 2022
Date: Thu, 22 Sep 2022 11:50:27 +0100	[thread overview]
Message-ID: <CAH6eHdToEca10omRVCtpppAF=xt6y0Uj6Rjh3J+aos_djhG6TA@mail.gmail.com> (raw)
In-Reply-To: <480509d3-1f72-ce6a-b966-91998e80d3cf@orange.fr>

On Thu, 22 Sept 2022 at 11:36, Jerome Huck wrote:
>
> Private communication.
>
> Hi.
>
> I am looking to be in touch with somebody at GNU GCC who is in charge of
> OpenACC integration in GCC.
>
> I am looking to be in touch with Tobias Burnus, Thomas Schwinge and
> Andrew Stubbs who made a presentation at Cauldron 2022 on the subject.

They'll probably see your email, but you can find contact details for
all GCC developers in the MAINTAINERS file:
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=MAINTAINERS;hb=HEAD

      reply	other threads:[~2022-09-22 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 10:36 Jerome Huck
2022-09-22 10:50 ` Jonathan Wakely [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='CAH6eHdToEca10omRVCtpppAF=xt6y0Uj6Rjh3J+aos_djhG6TA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jeromehuck.2022@orange.fr \
    /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).