public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge 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, 15 Apr 2021 17:20:07 +0000 [thread overview] Message-ID: <bug-90115-4-D2mJSeGAFe@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 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |90114 --- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Very much related is privatization via the corresponding 'private' clauses, at the respective level. (Thus not filing a new PR for that.) OpenACC 3.1, 2.5.12 "private clause" (similar 2.5.13 "firstprivate clause") states that on compute constructs, "The 'private' clause [...] declares that a copy of each item on the list will be created for each gang", and OpenACC 3.1, 2.9.10 "private clause" states: | The 'private' clause on a 'loop' construct specifies that a copy of each item in var-list will be created. If the body of the loop is executed in 'vector-partitioned' mode, a copy of the item is created for each thread associated with each vector lane. If the body of the loop is executed in 'worker-partitioned' 'vector-single' mode, a copy of the item is created for and shared across the set of threads associated with all the vector lanes of each worker. Otherwise, a copy of the item is created for and shared across the set of threads associated with all the vector lanes of all the workers of each gang. Also related is PR90114 "Predetermined private levels for variables declared in OpenACC accelerator routines". Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90114 [Bug 90114] Predetermined private levels for variables declared in OpenACC accelerator routines
next parent reply other threads:[~2021-04-15 17:20 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 [this message] 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 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-D2mJSeGAFe@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).