public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109771] Unnecessary pblendw for vectorized or
Date: Mon, 08 May 2023 16:03:56 +0000 [thread overview]
Message-ID: <bug-109771-4-q8Vky2POlT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109771-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109771
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|rtl-optimization |tree-optimization
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
vect_y_w_0_5.51_14 = MEM <vector(2) long unsigned int> [(void *)t_4(D)];
vect_y_w_0_5.52_10 = MEM <vector(2) long unsigned int> [(void *)t_4(D) +
16B];
vect_y_w_0_5.54_24 = MEM <vector(2) long unsigned int> [(void *)t_4(D) +
48B];
vect_y_w_0_5.55_6 = VEC_PERM_EXPR <vect_y_w_0_5.52_10, vect_y_w_0_5.54_24, {
0, 3 }>;
vect_x_w_0_36.60_44 = MEM <vector(2) long unsigned int> [(void *)t_4(D) +
32B];
vect_y_w_0_5.62_21 = VEC_PERM_EXPR <vect_y_w_0_5.54_24, vect_y_w_0_5.52_10, {
0, 3 }>;
vect__25.63_20 = vect_y_w_0_5.51_14 | vect_x_w_0_36.60_44;
vect__25.63_19 = vect_y_w_0_5.55_6 | vect_y_w_0_5.62_21;
MEM <vector(2) long unsigned int> [(long unsigned int *)t_4(D) + 32B] =
vect__25.63_20;
MEM <vector(2) long unsigned int> [(long unsigned int *)t_4(D) + 48B] =
vect__25.63_19;
vs
vect_y_w_0_10.25_44 = MEM <vector(2) long unsigned int> [(long unsigned int
*)t_2(D)];
vect_y_w_0_10.26_46 = MEM <vector(2) long unsigned int> [(long unsigned int
*)t_2(D) + 16B];
x = MEM[(const struct u256 &)t_2(D) + 32];
vect__6.14_9 = MEM <vector(2) long unsigned int> [(long unsigned int *)&x];
vect__8.18_14 = vect__6.14_9 | vect_y_w_0_10.25_44;
MEM <vector(2) long unsigned int> [(long unsigned int *)&z] = vect__8.18_14;
vect__6.14_11 = MEM <vector(2) long unsigned int> [(long unsigned int *)&x +
16B];
vect__8.18_36 = vect__6.14_11 | vect_y_w_0_10.26_46;
MEM <vector(2) long unsigned int> [(long unsigned int *)&z + 16B] =
vect__8.18_36;
x ={v} {CLOBBER(eol)};
MEM[(struct u256 *)t_2(D) + 32B] = z;
z ={v} {CLOBBER(eol)};
prev parent reply other threads:[~2023-05-08 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 13:58 [Bug rtl-optimization/109771] New: " chfast at gmail dot com
2023-05-08 16:01 ` [Bug rtl-optimization/109771] " pinskia at gcc dot gnu.org
2023-05-08 16:03 ` pinskia at gcc dot gnu.org [this message]
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-109771-4-q8Vky2POlT@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).