public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97390] [OpenAError compiling acc data present Date: Tue, 13 Oct 2020 17:33:14 +0000 [thread overview] Message-ID: <bug-97390-4-5aLLOVhbVO@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 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Error compiling acc data |[OpenAError compiling acc |present |data present --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Thomas Schwinge from comment #1) > Would it be the case that this line is longer than 132 characters? [...] > (I cannot comment on (a) why that's a useful limit to have I don't know whether it is useful or not, but the Fortran standard has: "In free source form [...] If a line consists entirely of characters of default kind (7.4.4), it shall contain at most 132 characters" (Fortran 2018, 6.3.2.1 Free form line length) > , and (b) whether the error reporting shouldn't be improved.) Well, the error message without changing the maximal supported line length is (GCC 9, 10 or 11): test.f90:2:132: 2 | !$acc data present(tempRbuffer, array, compactHaloInfo, dimsizes, nHaloLayers, gpu_nList_send, gpu_idx_send, gpu_bufferOffset_send) async(counter+1) | 1 Error: Syntax error in OpenMP variable list at (1) Which looks fine. However, my error message improvements for GCC 10 really help. With -ffree-line-length-none, the error is: With GCC 9's : Error: Unclassifiable OpenACC directive at (1) With GCC 10 or GCC 11: 2 | !$acc data present(tempRbuffer, array, compactHaloInfo, dimsizes, nHaloLayers, gpu_nList_send, gpu_idx_send, gpu_bufferOffset_send) async(counter+1) | 1 Error: Failed to match clause at (1) Note the '1' is at 'async(...)' I claim that GCC is right: 'acc data' does not have a 'async' clause in OpenACC neither in 2.6 (= supported by GCC 10) nor in 3.0; see https://www.openacc.org/specification BTW: Consider using GCC 10, which extended the OpenACC support, cf. https://gcc.gnu.org/gcc-10/changes.html
next prev parent reply other threads:[~2020-10-13 17:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 20:16 [Bug fortran/97390] New: Error " 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 2020-10-13 17:33 ` burnus at gcc dot gnu.org [this message] 2020-10-13 21:55 ` [Bug fortran/97390] [OpenACC] " 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-5aLLOVhbVO@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).