public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100321] [OpenMP][nvptx, SIMT] (Con't) Reduction fails with optimization and 'loop'/'for simd' but not with 'for'
Date: Mon, 03 May 2021 10:26:21 +0000 [thread overview]
Message-ID: <bug-100321-4-mLJC3IC9A5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100321-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100321
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> So, something like this reflects the current state:
> ...
> diff --git a/gcc/omp-low.c b/gcc/omp-low.c
> index 7b122059c6e..a0561800977 100644
> --- a/gcc/omp-low.c
> +++ b/gcc/omp-low.c
> @@ -6005,6 +6005,11 @@ lower_rec_input_clauses (tree clauses, gimple_seq
> *ilist, gimple_seq *dlist,
> tree placeholder = OMP_CLAUSE_REDUCTION_PLACEHOLDER (c);
> gimple *tseq;
> tree ptype = TREE_TYPE (placeholder);
> + if (sctx.is_simt)
> + {
> + sorry ("SIMT not fully implemented");
> + abort ();
> + }
> if (cond)
> {
> x = error_mark_node;
> ...
Submitted patch that does something similar (but using error rather than
sorry/abort) @ https://gcc.gnu.org/pipermail/gcc-patches/2021-May/569421.html .
next prev parent reply other threads:[~2021-05-03 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 15:36 [Bug target/100321] New: [OpenMP][nvptx] " burnus at gcc dot gnu.org
2021-04-28 21:15 ` [Bug target/100321] " vries at gcc dot gnu.org
2021-04-29 6:24 ` [Bug target/100321] [OpenMP][nvptx, SIMT] " vries at gcc dot gnu.org
2021-04-29 15:09 ` vries at gcc dot gnu.org
2021-04-29 15:18 ` vries at gcc dot gnu.org
2021-05-03 10:26 ` vries at gcc dot gnu.org [this message]
2021-05-03 21:14 ` cvs-commit at gcc dot gnu.org
2021-05-03 21:15 ` 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-100321-4-mLJC3IC9A5@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).