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/82426] Missed tree-slp-vectorization on -O2 and -O3
Date: Wed, 25 Aug 2021 07:13:07 +0000 [thread overview]
Message-ID: <bug-82426-4-7j1toKt54f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82426-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82426
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
x86 actually does have V2SF, the issue is that there's an opportunity for V4SF
vectorization and one for V2SF arriving at the same load groups and that causes
a conflict (there's other PRs about this general issue), so we kill one part:
t.C:18:12: missed: desired vector type conflicts with earlier one for _2 =
b_35(D)->m11;
t.C:18:12: note: removing SLP instance operations starting from: <retval>.dx =
_27;
also we have a bunch of live lanes off the remaining vectorized piece which
makes code a bit awkward.
Unfortunately we have no way to force 64bit vectors here (V2SF) to see whether
splitting up the V4SFmode partition would help (I guess it would as can be
seen from using 'double').
next prev parent reply other threads:[~2021-08-25 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82426-4@http.gcc.gnu.org/bugzilla/>
2021-08-25 0:13 ` pinskia at gcc dot gnu.org
2021-08-25 7:13 ` rguenth at gcc dot gnu.org [this message]
2021-09-20 11:11 ` rguenth at gcc dot gnu.org
2021-09-27 8:24 ` cvs-commit at gcc dot gnu.org
2021-09-27 8:26 ` 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-82426-4-7j1toKt54f@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).