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/98915] OpenACC 'routine with a name' directive does not compile
Date: Mon, 01 Feb 2021 14:19:11 +0000	[thread overview]
Message-ID: <bug-98915-4-3UeMzpKS7Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98915-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98915

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(Now: OpenACC spec issue #345)

I am not sure that a use as in attachment 50106 is really intended, namely:
placing the "acc routine" into a sibling procedure.

However, gfortran seems to reject too much – at least with the current wording.

The problem is that the diagnostic already happens at call time
(gfc_match_oacc_routine) which requires that the symbol has been encountered
before (during parsing) and the usage is such that it has to be in the current
scope and cannot be in the parent scope.

      parent reply	other threads:[~2021-02-01 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 11:49 [Bug fortran/98915] New: OpenACC routine with a name " kd486 at cam dot ac.uk
2021-02-01 11:58 ` [Bug fortran/98915] " kd486 at cam dot ac.uk
2021-02-01 14:19 ` burnus at gcc dot gnu.org [this message]

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-98915-4-3UeMzpKS7Q@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).