From: Vikram Singh <vikramsingh001@gmail.com>
To: fortran@gcc.gnu.org
Subject: OpenACC-Library-Interoperability
Date: Tue, 12 Apr 2016 15:00:00 -0000 [thread overview]
Message-ID: <CAD0gq3XehzKyOqvqWfmSErNiy8CKkHqNvqAg5nU5eCyV5gQ4RA@mail.gmail.com> (raw)
We have a project that is written in gfortran.
I am trying to see whether we could use OpenACC in our project. I got
gcc5.2 installed using instructions here.
https://github.com/olcf/OLCFHack15
Now I want to do something similar to what is stated here.
https://gcc.gnu.org/onlinedocs/libgomp/OpenACC-Library-Interoperability.html
More specifically what is stated in secion 8.3. I am trying to exactly
reproduce it using gfortran. Unfortunately I don't see how I can do it
in fortran. In the example,
d_X = acc_copyin(&h_X[0], N * sizeof (float));
This allows d_X to be directly used in s = cublasSaxpy(h, N, &alpha,
d_X, 1, d_Y, 1);
But in fortran, the acc_copyin does not return anything.
So how would I replicate the case in Fortran?
Thanks and Regards,
Vikram
next reply other threads:[~2016-04-12 15:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 15:00 Vikram Singh [this message]
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 ` OpenACC-Library-Interoperability Thomas Schwinge
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=CAD0gq3XehzKyOqvqWfmSErNiy8CKkHqNvqAg5nU5eCyV5gQ4RA@mail.gmail.com \
--to=vikramsingh001@gmail.com \
--cc=fortran@gcc.gnu.org \
/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).