public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96481] SLP fail to vectorize VEC_COND_EXPR pattern.
Date: Wed, 05 Aug 2020 11:30:15 +0000 [thread overview]
Message-ID: <bug-96481-4-pK9tB9xnGL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96481-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96481
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> So in theory we could record basic-block boundaries as DR group_id instead
Note for outer loop vect we need the BB restriction which means we'd need to
compute the group_id array also for loop vect.
next prev parent reply other threads:[~2020-08-05 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 9:26 [Bug tree-optimization/96481] New: " crazylht at gmail dot com
2020-08-05 11:26 ` [Bug tree-optimization/96481] " rguenth at gcc dot gnu.org
2020-08-05 11:28 ` rguenth at gcc dot gnu.org
2020-08-05 11:30 ` rguenth at gcc dot gnu.org [this message]
2020-08-10 3:20 ` marxin at gcc dot gnu.org
2021-08-19 23:13 ` pinskia at gcc dot gnu.org
2021-08-20 9:18 ` rguenth at gcc dot gnu.org
2021-08-20 10:46 ` rguenth 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-96481-4-pK9tB9xnGL@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).