From: Thomas Koenig <tkoenig@netcologne.de>
To: Thomas Schwinge <thomas@codesourcery.com>,
gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Cc: Tobias Burnus <burnus@net-b.de>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PR72741] Encode OpenACC 'routine' directive's level of parallelism inside Fortran module files
Date: Thu, 21 Mar 2019 20:49:00 -0000 [thread overview]
Message-ID: <9f6ba8a0-fd46-631e-b8eb-67423e4796f3@netcologne.de> (raw)
In-Reply-To: <87ftrhsvq9.fsf@euler.schwinge.homeip.net>
Hi Thomas,
> Are there any further questions, or am I good to commit my patch as
> posted?
Problem is, I have never looked into module writing / reading in any
detail, so it will take a few days for me to get up to speed so I can
really review your patch.
If, in the meantime, maybe somebody else with more knowledge in that
area (Janne?) could step in.
Regards
Thomas
next prev parent reply other threads:[~2019-03-21 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 3:12 [PATCH,openacc] check for compatible loop parallelism with acc routine calls Cesar Philippidis
2016-06-17 14:42 ` Jakub Jelinek
2016-06-23 16:05 ` Cesar Philippidis
2016-06-29 14:11 ` Thomas Schwinge
2016-06-29 14:35 ` Jakub Jelinek
2016-06-29 15:31 ` Cesar Philippidis
2019-02-28 21:12 ` [PR72741] Encode OpenACC 'routine' directive inside Fortran module files Thomas Schwinge
2019-02-28 21:17 ` Jakub Jelinek
2019-03-13 17:50 ` [PR72741] Encode OpenACC 'routine' directive's level of parallelism " Thomas Schwinge
2019-03-13 22:13 ` Thomas Koenig
2019-03-14 7:38 ` Thomas Schwinge
2019-03-20 10:09 ` Thomas Schwinge
2019-03-21 20:49 ` Thomas Koenig [this message]
2019-03-21 19:47 ` Thomas Schwinge
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=9f6ba8a0-fd46-631e-b8eb-67423e4796f3@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=thomas@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).