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: Fri, 21 May 2021 18:54:56 +0000 [thread overview] Message-ID: <bug-90115-4-jd1PLSgO0e@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 #8 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:5a0fe1f6c4ad0e50bf4684e723ae2ba17d94c9e4 commit r12-986-g5a0fe1f6c4ad0e50bf4684e723ae2ba17d94c9e4 Author: Thomas Schwinge <thomas@codesourcery.com> Date: Thu May 20 15:55:18 2021 +0200 [OpenACC privatization] Explain OpenACC privatization candidate selection [PR90115] gcc/ PR middle-end/90115 * omp-low.c (oacc_privatization_candidate_p): New function. (oacc_privatization_scan_clause_chain) (oacc_privatization_scan_decl_chain): Use it. Also 'gcc_checking_assert' that we're not seeing duplicates.
next prev parent reply other threads:[~2021-05-21 18:54 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 [this message] 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 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-jd1PLSgO0e@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).