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 middle-end/94120] [OpenACC] ICE in gimplify_adjust_omp_clauses_1 for 'declare' for variable outside scope
Date: Wed, 08 Apr 2020 07:40:59 +0000	[thread overview]
Message-ID: <bug-94120-4-YBNTaFY0Ku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94120-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:13e41d8b9d3d7598c72c38acc86a3d97046c8373

commit r10-7614-g13e41d8b9d3d7598c72c38acc86a3d97046c8373
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Apr 8 09:39:43 2020 +0200

    [C/C++, OpenACC] Reject vars of different scope in acc declare (PR94120)

            gcc/c/
            PR middle-end/94120
            * c-decl.c (c_check_in_current_scope): New function.
            * c-tree.h (c_check_in_current_scope): Declare it.
            * c-parser.c (c_parser_oacc_declare): Add check that variables
            are declared in the same scope as the directive. Fix handling
            of namespace vars.

            gcc/cp/
            PR middle-end/94120
            * paser.c (cp_parser_oacc_declare): Add check that variables
            are declared in the same scope as the directive.

            gcc/testsuite/
            PR middle-end/94120
            * c-c++-common/goacc/declare-pr94120.c: New.
            * g++.dg/declare-pr94120.C: New.

            libgomp/testsuite/
            PR middle-end/94120
            * libgomp.oacc-c++/declare-pr94120.C: New.

  parent reply	other threads:[~2020-04-08  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 11:47 [Bug middle-end/94120] New: " burnus at gcc dot gnu.org
2020-03-10 12:11 ` [Bug middle-end/94120] " marxin at gcc dot gnu.org
2020-03-10 14:21 ` burnus at gcc dot gnu.org
2020-03-10 17:22 ` burnus at gcc dot gnu.org
2020-03-11 13:31 ` burnus at gcc dot gnu.org
2020-03-12 10:47 ` burnus at gcc dot gnu.org
2020-04-08  7:40 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-08  7:48 ` burnus at gcc dot gnu.org
2020-04-08 17:56 ` cvs-commit at gcc dot gnu.org
2020-04-20 10:42 ` cvs-commit 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-94120-4-YBNTaFY0Ku@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).