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/90115] OpenACC: predetermined private levels for variables declared in blocks Date: Thu, 10 Mar 2022 11:07:00 +0000 [thread overview] Message-ID: <bug-90115-4-bh7XaKwErb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90115-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90115 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>: https://gcc.gnu.org/g:1d9dc3dd74eddd192bec1ac6f4d6548a81deb9a5 commit r12-7577-g1d9dc3dd74eddd192bec1ac6f4d6548a81deb9a5 Author: Thomas Schwinge <thomas@codesourcery.com> Date: Tue Mar 8 11:51:55 2022 +0100 Enhance further testcases to verify handling of OpenACC privatization level [PR90115] As originally introduced in commit 11b8286a83289f5b54e813f14ff56d730c3f3185 "[OpenACC privatization] Largely extend diagnostics and corresponding testsuite coverage [PR90115]". PR middle-end/90115 gcc/testsuite/ * c-c++-common/goacc/nesting-1.c: Enhance. * gcc.dg/goacc/nested-function-1.c: Likewise. * gcc.dg/goacc/nested-function-2.c: Likewise. * gfortran.dg/goacc/nested-function-1.f90: Likewise. libgomp/ * testsuite/libgomp.oacc-fortran/routine-1.f90: Enhance. * testsuite/libgomp.oacc-fortran/routine-2.f90: Likewise. * testsuite/libgomp.oacc-fortran/routine-3.f90: Likewise. * testsuite/libgomp.oacc-fortran/routine-9.f90: Likewise.
next prev parent reply other threads:[~2022-03-10 11:07 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90115-4@http.gcc.gnu.org/bugzilla/> 2021-04-15 17:20 ` tschwinge at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:54 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:55 ` cvs-commit at gcc dot gnu.org 2021-05-21 18:55 ` cvs-commit at gcc dot gnu.org 2021-05-22 8:38 ` cvs-commit at gcc dot gnu.org 2022-03-02 2:19 ` egallager at gcc dot gnu.org 2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org 2022-03-10 11:34 ` tschwinge at gcc dot gnu.org 2022-03-12 13:04 ` cvs-commit at gcc dot gnu.org 2022-03-17 7:54 ` cvs-commit at gcc dot gnu.org 2022-10-28 8:25 ` cvs-commit at gcc dot gnu.org 2022-10-28 8:31 ` 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-90115-4-bh7XaKwErb@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).