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/101801] vect_worthwhile_without_simd_p is broken
Date: Fri, 06 Aug 2021 11:21:21 +0000 [thread overview]
Message-ID: <bug-101801-4-2dHf8PAr6K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101801-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101801
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to rsandifo@gcc.gnu.org from comment #3)
> So maybe a less invasive fix would be to add && !VECTOR_BOOLEAN_TYPE_P
> to the condition. Still no objection to killing it off instead though.
Yeah, I've pondered adding && !mask_op_p - but I'm not sure if
VECTOR_BOOLEAN_TYPE_P can be generic vectors (I guess not at the moment).
So detecting what is a generic vector and what not seems fragile.
Btw, we _do_ vectorize using vector booleans, it's just the check
for vect_worthwhile_without_simd_p misclassifies the non-vector-mode
types as "generic".
I'm currently checking whether there's any testsuite fallout in making
vect_worthwhile_without_simd_p return true unconditionally.
next prev parent reply other threads:[~2021-08-06 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 10:26 [Bug tree-optimization/101801] New: " rguenth at gcc dot gnu.org
2021-08-06 10:27 ` [Bug tree-optimization/101801] " rguenth at gcc dot gnu.org
2021-08-06 11:09 ` rsandifo at gcc dot gnu.org
2021-08-06 11:12 ` rsandifo at gcc dot gnu.org
2021-08-06 11:21 ` rguenth at gcc dot gnu.org [this message]
2021-08-06 13:32 ` cvs-commit at gcc dot gnu.org
2021-08-06 13:33 ` rguenth at gcc dot gnu.org
2021-08-10 8:12 ` cvs-commit at gcc dot gnu.org
2021-08-25 2:32 ` pinskia 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-101801-4-2dHf8PAr6K@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).