public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Vikram Singh <vikramsingh001@gmail.com>
Cc: James Norris <jnorris@codesourcery.com>,
	Chung-Lin Tang	<cltang@codesourcery.com>, <fortran@gcc.gnu.org>
Subject: Re: OpenACC-Library-Interoperability
Date: Fri, 15 Apr 2016 08:58:00 -0000	[thread overview]
Message-ID: <8760vj45bi.fsf@hertz.schwinge.homeip.net> (raw)
In-Reply-To: <CAD0gq3XgHLLWfY8BJWCc2vPC6S4E2tHBvBfdok0yK5Gs4K5Qzw@mail.gmail.com>

Hi Vikram!

On Fri, 15 Apr 2016 11:35:06 +0300, Vikram Singh <vikramsingh001@gmail.com> wrote:
> Yes, I came to the conclusion that host_data
> would be the only way to do it in fortran.
> 
> On the other hand, I though there were no plans to implement it in
> gfortran 6 either

I still hope we'll get this (that is, <https://gcc.gnu.org/PR70598>)
fixed in time for the GCC 6.1 release.  I'll keep you posted.


> > I'm copying Jim, who is the author of this chapter in the documentation
> > as well as the libgomp/testsuite/libgomp.oacc-c-c++-common/context-*.c
> > test cases, and much of the relevant libgomp code, too, and who should
> > please correct me if I'm wrong.  I'll make a note for later, that we
> > should translate the libgomp.oacc-c-c++-common/context-*.c test cases to
> > Fortran, and also replicate them using the OpenACC host_data construct
> > (like in libgomp/testsuite/libgomp.oacc-c-c++-common/host_data-1.c), and
> > the same for the documentation you referenced.  (Vikram, please tell if
> > you're interested to work on these items.)
> 
> I am not sure I understand what you want me to work on exactly. I am
> not really much of a C programmer, so I wouldn't be good at it. I
> would still like to help.

Sorry for being unclear.  My idea/question has been whether you're
interested in helping by translating the documentation as well as the
libgomp.oacc-c-c++-common/context-*.c test cases from C to Fortran (using
the OpenACC host_data construct instead of the acc_* functions).  If yes,
then that's great, if not, then one of us will do it at some point.


Grüße
 Thomas

  reply	other threads:[~2016-04-15  8:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 15:00 OpenACC-Library-Interoperability Vikram Singh
2016-04-15  6:16 ` OpenACC-Library-Interoperability Thomas Schwinge
2016-04-15  8:36   ` OpenACC-Library-Interoperability Vikram Singh
2016-04-15  8:58     ` Thomas Schwinge [this message]
2016-04-15 11:00       ` OpenACC-Library-Interoperability Vikram Singh
2016-05-12 15:35         ` OpenACC-Library-Interoperability Thomas Schwinge
2016-05-12 16:41           ` OpenACC-Library-Interoperability Vikram Singh
2016-05-12 17:54             ` OpenACC-Library-Interoperability Vikram Singh
     [not found]           ` <CAD0gq3VoRWCiXRkgi-bnGLBfSjR-bFc0Mzp19LRr+yWP4MrYLg@mail.gmail.com>
     [not found]             ` <CANSzZf6md-w8SZOJEeawThYbVfH0cLgNRS9r5VaADqZKdy6KtA@mail.gmail.com>
2016-08-02 16:56               ` OpenACC-Library-Interoperability Salvatore Filippone
2016-08-03 15:53             ` OpenACC-Library-Interoperability Vikram Singh
2016-08-29 13:59               ` OpenACC-Library-Interoperability Vikram Singh
2016-08-29 14:05                 ` OpenACC-Library-Interoperability James Norris
2016-08-29 14:15                   ` OpenACC-Library-Interoperability Vikram Singh
2016-08-29 14:34                 ` OpenACC-Library-Interoperability Cesar Philippidis
2016-08-29 15:39                   ` OpenACC-Library-Interoperability Vikram Singh
2016-08-29 16:16                     ` OpenACC-Library-Interoperability Cesar Philippidis
2016-08-31  9:43                       ` OpenACC-Library-Interoperability Vikram Singh
     [not found] <CAKe2ite0OWGjtQtHkLY-FDxqJLXmDbKAWOiRLqTP+cUS1-qWog@mail.gmail.com>
2016-04-27 17:16 ` OpenACC-Library-Interoperability Vladimír Fuka
2016-04-15 14:36   ` OpenACC-Library-Interoperabilit Salvatore Filippone
2016-05-09 14:27     ` [PATCH, Fortran, OpenACC] Fix PR70598, Fortran host_data ICE Chung-Lin Tang
2016-05-10 18:58       ` Bernhard Reutner-Fischer
2016-06-07 12:04         ` Chung-Lin Tang
2016-06-21  6:18           ` [PATCH, Fortran, OpenACC] Fix PR70598, Fortran host_data ICE (ping x2) Chung-Lin Tang
2016-07-13 11:53             ` [PATCH, Fortran, OpenACC] Fix PR70598, Fortran host_data ICE (ping x3) Chung-Lin Tang
2016-07-21  9:29               ` [PATCH, Fortran, OpenACC] Fix PR70598, Fortran host_data ICE (ping x4) Chung-Lin Tang
2016-07-21 10:54                 ` Paul Richard Thomas
2016-07-21 11:13       ` [PATCH, Fortran, OpenACC] Fix PR70598, Fortran host_data ICE Jakub Jelinek
2016-07-29 15:47         ` Chung-Lin Tang
2016-08-09 15:30           ` Jakub Jelinek

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=8760vj45bi.fsf@hertz.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=cltang@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=jnorris@codesourcery.com \
    --cc=vikramsingh001@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).