public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90111] Placement of Fortran OpenACC 'routine' directive inside 'specification-part'
Date: Mon, 09 Nov 2020 15:20:06 +0000	[thread overview]
Message-ID: <bug-90111-4-GHH9sIx3Yp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90111-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:f27a3b37b4805feba138dd421f039e3267b1c5f0

commit r11-4845-gf27a3b37b4805feba138dd421f039e3267b1c5f0
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Mon Nov 9 16:16:44 2020 +0100

    Fortran: Fix OpenACC in specification-part checks [PR90111]

    OpenACC's routine and declare directives can appear anywhere in the
    specification part, i.e. before/after use-stmts, import-stmt,
implicit-part,
    or declaration-constructs.

    gcc/fortran/ChangeLog:

            PR fortran/90111
            * parse.c (case_decl): Move ST_OACC_ROUTINE and ST_OACC_DECLARE to
...
            (case_omp_decl): ... here.
            (verify_st_order): Update comment.

    gcc/testsuite/ChangeLog:

            PR fortran/90111
            * gfortran.dg/goacc/specification-part.f90: New test.

       reply	other threads:[~2020-11-09 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90111-4@http.gcc.gnu.org/bugzilla/>
2020-11-09 15:20 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-09 15:23 ` burnus 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-90111-4-GHH9sIx3Yp@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).