public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104952] [nvptx][OpenMP] wrong code with OR / AND reduction ('reduction(||:' and '&&') with SIMT Date: Thu, 17 Mar 2022 13:04:20 +0000 [thread overview] Message-ID: <bug-104952-4-eHUCZUUFhx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104952-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104952 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, I guess this is related to PR94366 and r12-438-g1580fc764423bf89e9b which was fixing it for non-SIMT and quite possibly left out the SIMT stuff out. Using the TRUTH_{AND,OR}_EXPR instead of TRUTH_{AND,OR}IF_EXPR ought to be fine, it is only merging the private vars into the original var, so neither has really side-effects, all we want is that we are actually merging orig = (orig != 0) & (private != 0) rather than orig & private etc.
next prev parent reply other threads:[~2022-03-17 13:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-16 11:42 [Bug target/104952] New: " burnus at gcc dot gnu.org 2022-03-17 10:30 ` [Bug target/104952] " vries at gcc dot gnu.org 2022-03-17 12:07 ` vries at gcc dot gnu.org 2022-03-17 12:46 ` vries at gcc dot gnu.org 2022-03-17 12:56 ` vries at gcc dot gnu.org 2022-03-17 13:04 ` jakub at gcc dot gnu.org [this message] 2022-03-17 13:14 ` jakub at gcc dot gnu.org 2022-03-17 13:29 ` vries at gcc dot gnu.org 2022-03-17 13:31 ` vries at gcc dot gnu.org 2022-03-17 14:12 ` vries at gcc dot gnu.org 2022-03-17 14:17 ` jakub at gcc dot gnu.org 2022-03-18 14:46 ` cvs-commit at gcc dot gnu.org 2022-03-18 14:48 ` vries 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-104952-4-eHUCZUUFhx@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).