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] New: Error compiling acc data present
Date: Mon, 12 Oct 2020 20:16:29 +0000 [thread overview]
Message-ID: <bug-97390-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97390
Bug ID: 97390
Summary: Error compiling acc data present
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: afernandez at odyhpc dot com
Target Milestone: ---
Hello,
While trying to compile an app with gfortran 9.3.0 & -fopenacc, the compiler
doesn't seem to recognize some directive and causes the following error
message:
6475 | !$acc data present(tempRbuffer, array, compactHaloInfo,
dimsizes, nHaloLayers, gpu_nList_send, gpu_idx_send, gpu_bufferOffset_send)
async(counter+1)
| 1
Error: Unclassifiable OpenACC directive at (1)
The compiler recognizes other OpenACC directives but this error happens at
several points of the code. I'm not the developer and the app is supposed to
compile smoothly with the PGI compiler. Could this problem be caused by the
compiler or should I be looking at some specific conflict? Thanks.
next reply other threads:[~2020-10-12 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:16 afernandez at odyhpc dot com [this message]
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
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@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: 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).