public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <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: Thu, 07 Jul 2022 05:40:53 +0000	[thread overview]
Message-ID: <bug-106180-4-dRYSBDdMDs@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 #9 from Haochen Jiang <haochen.jiang at intel dot com> ---
(In reply to Haochen Jiang from comment #8)
> Created attachment 53269 [details]
> This patch aims to handle memory issue when unpacking in cvtps2pd (version 2)
> 
> Just fully tested on this patch. Changed to adjust_address_nv to reduce
> function calls.

What I mean by fully tested is regtested on x86_64-pc-linux-gnu.

  parent reply	other threads:[~2022-07-07  5:40 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
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 [this message]
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-dRYSBDdMDs@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).