public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106180] [13 Regression] ICE in extract_insn, at recog.cc:2791 since r13-1418-g73f942c08deef3
Date: Tue, 05 Jul 2022 12:26:52 +0000	[thread overview]
Message-ID: <bug-106180-4-xT2CHVZzap@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106180-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106180

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That doesn't really matter, many instructions just use the g, q etc. modifiers
so that the correct Intel syntax is written, the RTL can have larger MEM just
fine, the only thing that is wrong is e.g. if the expander has V2SF operand to
widen it  to V4SF using a subreg.  But if you match an instruction that had
V4SF operand, the fact that you actually just read 8 bytes from it rather than
16 isn't that bad.  Especially for the unpacks which are paired, one hi and one
lo which together read the whole memory anyway.

  parent reply	other threads:[~2022-07-05 12:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 10:08 [Bug target/106180] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 since 73f942c08deef3cce312263b3347f7a44dd44150 marxin at gcc dot gnu.org
2022-07-04 10:09 ` [Bug target/106180] [13 Regression] ICE in extract_insn, at recog.cc:2791 since r13-1418-g73f942c08deef3 marxin at gcc dot gnu.org
2022-07-04 10:56 ` jakub at gcc dot gnu.org
2022-07-04 11:59 ` rguenth at gcc dot gnu.org
2022-07-05  2:11 ` wwwhhhyyy333 at gmail dot com
2022-07-05 12:26 ` jakub at gcc dot gnu.org [this message]
2022-07-06  1:39 ` haochen.jiang at intel dot com
2022-07-06 19:53 ` dcb314 at hotmail dot com
2022-07-06 20:07 ` ubizjak at gmail dot com
2022-07-07  3:23 ` haochen.jiang at intel dot com
2022-07-07  5:39 ` haochen.jiang at intel dot com
2022-07-07  5:40 ` haochen.jiang at intel dot com
2022-07-08  4:18 ` cvs-commit at gcc dot gnu.org
2022-10-19 10:35 ` 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-106180-4-xT2CHVZzap@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).