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 target/94866] Failure to optimize pinsrq of 0 with index 1 into movq
Date: Thu, 30 Apr 2020 07:13:27 +0000 [thread overview]
Message-ID: <bug-94866-4-4YqzX1BtUB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94866-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-04-30
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Depends on| |94864
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
We're expanding from
_3 = BIT_INSERT_EXPR <a_1(D), 0, 64 (64 bits)>;
return _3;
which ends up using
(insn 8 7 9 (set (reg:V2DI 85)
(vec_merge:V2DI (vec_duplicate:V2DI (reg:DI 86))
(reg:V2DI 85)
(const_int 2 [0x2]))) "y.c":6:28 -1
so likely the vec_merge "issue" again.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94864
[Bug 94864] Failure to combine vunpckhpd+movsd into single vunpckhpd
next prev parent reply other threads:[~2020-04-30 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 0:21 [Bug target/94866] New: " gabravier at gmail dot com
2020-04-30 7:13 ` rguenth at gcc dot gnu.org [this message]
2023-08-22 9:35 ` [Bug target/94866] " rguenth at gcc dot gnu.org
2023-08-22 12:43 ` ubizjak at gmail dot com
2023-08-23 1:12 ` crazylht at gmail dot com
2023-08-23 11:21 ` ubizjak at gmail dot com
2023-08-23 11:23 ` ubizjak at gmail dot com
2023-08-23 13:39 ` crazylht at gmail dot com
2023-08-23 14:54 ` ubizjak at gmail dot com
2023-08-24 1:12 ` crazylht at gmail dot com
2023-08-24 20:25 ` cvs-commit at gcc dot gnu.org
2023-08-24 20:27 ` ubizjak 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-94866-4-4YqzX1BtUB@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).