public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102583] [x86] Failure to optimize 32-byte integer vector conversion to 16-byte float vector properly when converting upper part with -mavx2
Date: Tue, 25 Jan 2022 09:06:19 +0000 [thread overview]
Message-ID: <bug-102583-4-YSFk7Apr7h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102583-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102583
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #2)
> Simplify
> _4 = VEC_PERM_EXPR <_1, _1, { 4, 5, 6, 7, 4, 5, 6, 7 }>;
> _5 = BIT_FIELD_REF <_4, 128, 0>;
>
> to
>
> _5 = BIT_FIELD_REF <_1, 128, 128>;
>
> in match.pd?
maybe forwprop this
15 _1 = *srcp_7(D);
16 _2 = BIT_FIELD_REF <_1, 32, 128>;
17 _3 = BIT_FIELD_REF <_1, 32, 160>;
18 _4 = BIT_FIELD_REF <_1, 32, 192>;
19 _5 = BIT_FIELD_REF <_1, 32, 224>;
20 b_9 = {_2, _3, _4, _5};
directly into
b_9 = BIT_FIELD_REF <*srcp_7, 128, 128>;
next prev parent reply other threads:[~2022-01-25 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 2:57 [Bug target/102583] New: " gabravier at gmail dot com
2021-10-04 7:53 ` [Bug target/102583] " rguenth at gcc dot gnu.org
2022-01-25 6:32 ` [Bug tree-optimization/102583] " crazylht at gmail dot com
2022-01-25 9:06 ` crazylht at gmail dot com [this message]
2022-04-08 7:28 ` crazylht at gmail dot com
2022-05-13 1:04 ` cvs-commit at gcc dot gnu.org
2022-05-13 1:19 ` crazylht at gmail dot com
2022-05-16 22:11 ` gabravier at gmail dot com
2022-05-16 23:09 ` hjl.tools at gmail dot com
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-102583-4-YSFk7Apr7h@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).