public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager 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: Wed, 02 Mar 2022 02:19:19 +0000 [thread overview]
Message-ID: <bug-90115-4-lXarW6m8OX@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
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #12 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #11)
> The master branch has been updated by Thomas Schwinge
> <tschwinge@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:3050a1a18276d7cdd8946e34cc1344e30efb7030
>
> commit r12-996-g3050a1a18276d7cdd8946e34cc1344e30efb7030
> Author: Thomas Schwinge <thomas@codesourcery.com>
> Date: Sat May 22 10:28:34 2021 +0200
>
> [OpenACC privatization] Prune uninteresting/varying diagnostics in
> 'libgomp.oacc-fortran/privatized-ref-2.f90'
>
> Minor fix-up for my recent commit
> 11b8286a83289f5b54e813f14ff56d730c3f3185
> "[OpenACC privatization] Largely extend diagnostics and corresponding
> testsuite
> coverage [PR90115]".
>
> libgomp/
> PR testsuite/90115
> * testsuite/libgomp.oacc-fortran/privatized-ref-2.f90: Prune
> uninteresting/varying diagnostics.
>
> Reported-by: Sunil K Pandey <skpandey@sc.intel.com>
So, is it fixed now?
next prev parent reply other threads:[~2022-03-02 2:19 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 [this message]
2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org
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-lXarW6m8OX@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).