public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Translate libgomp.oacc-c-c++-common/lib-32.c into Fortran (was: C/C++ OpenACC: acc_pcopyin, acc_pcreate)
Date: Tue, 23 May 2017 11:12:00 -0000	[thread overview]
Message-ID: <20170523110822.GR8499@tucnak> (raw)
In-Reply-To: <878tlpynfk.fsf@hertz.schwinge.homeip.net>

On Mon, May 22, 2017 at 04:29:51PM +0200, Thomas Schwinge wrote:
> Hi!
> 
> On Mon, 22 May 2017 16:26:48 +0200, I wrote:
> >     C/C++ OpenACC: acc_pcopyin, acc_pcreate
> 
> >             libgomp/
> >             [...]
> >             * testsuite/libgomp.oacc-c-c++-common/lib-38.c: Remove, merging
> >             its content into...
> >             * testsuite/libgomp.oacc-c-c++-common/lib-32.c: ... this file.
> >             Extend testing.
> 
> ... which I then translated into two Fortran variants; OK for trunk?
> 
> commit 04ee44504e6256ee95ae3c6ba91a5960265b3261
> Author: Thomas Schwinge <thomas@codesourcery.com>
> Date:   Wed Apr 19 15:38:51 2017 +0200
> 
>     Translate libgomp.oacc-c-c++-common/lib-32.c into Fortran
>     
>             libgomp/
>             * testsuite/libgomp.oacc-fortran/lib-32-1.f: New file.
>             * testsuite/libgomp.oacc-fortran/lib-32-2.f: Likewise.

Ok.

	Jakub

  reply	other threads:[~2017-05-23 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 14:28 C/C++ OpenACC: acc_pcopyin, acc_pcreate Thomas Schwinge
2017-05-22 15:23 ` Translate libgomp.oacc-c-c++-common/lib-32.c into Fortran (was: C/C++ OpenACC: acc_pcopyin, acc_pcreate) Thomas Schwinge
2017-05-23 11:12   ` Jakub Jelinek [this message]
2017-05-24 13:45     ` Translate libgomp.oacc-c-c++-common/lib-32.c into Fortran Thomas Schwinge
2017-05-23 11:08 ` C/C++ OpenACC: acc_pcopyin, acc_pcreate Jakub Jelinek
2017-05-24 10:57   ` Thomas Schwinge
2017-05-24 11:24     ` Jakub Jelinek
2017-05-24 13:41       ` 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=20170523110822.GR8499@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).