public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "afernandez at odyhpc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97390] Error compiling acc data present Date: Tue, 13 Oct 2020 15:38:44 +0000 [thread overview] Message-ID: <bug-97390-4-rGeir6BvAu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97390-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97390 --- Comment #4 from afernandez at odyhpc dot com --- The code can be downloaded from GitHub: git clone https://github.com/MPAS-Dev/MPAS-Model cd MPAS-Model git checkout atmosphere/v6.x-openacc My experience with OpenACC is limited as I participated in a workshop 3 years ago but haven't used it since then. Yesterday I began to read some documentation (to refresh my memory) and the OpenACC 2.6 reference guide (https://www.openacc.org/sites/default/files/inline-files/OpenACC%20API%202.6%20Reference%20Guide.pdf) led me to think of this contruct as a standard one. Could this be an enhancement of 2.6 versus 2.5? If this were the case, would moving GNU from version 9 to 10 help? I'm unfamiliar with the PGI compilers so someone else might be able to chime in and shed some light on any PGI implementation.
next prev parent reply other threads:[~2020-10-13 15:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 20:16 [Bug fortran/97390] New: " afernandez at odyhpc dot com 2020-10-13 8:11 ` [Bug fortran/97390] " tschwinge at gcc dot gnu.org 2020-10-13 13:56 ` afernandez at odyhpc dot com 2020-10-13 14:48 ` tschwinge at gcc dot gnu.org 2020-10-13 15:38 ` afernandez at odyhpc dot com [this message] 2020-10-13 17:33 ` [Bug fortran/97390] [OpenAError " burnus at gcc dot gnu.org 2020-10-13 21:55 ` [Bug fortran/97390] [OpenACC] Error " afernandez at odyhpc dot com 2020-10-14 8:34 ` [Bug fortran/97390] [OpenACC] 'async' clause on 'data' construct tschwinge at gcc dot gnu.org 2020-10-14 13:53 ` cvs-commit at gcc dot gnu.org 2022-01-11 16:31 ` tschwinge at gcc dot gnu.org
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=bug-97390-4-rGeir6BvAu@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).