From: "Li, Pan2" <pan2.li@intel.com>
To: Jakub Jelinek <jakub@redhat.com>, Kito Cheng <kito.cheng@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: RE: [PATCH v2] RISC-V: Fix ICE for legitimize move on subreg const_poly_int [PR114885]
Date: Mon, 29 Apr 2024 08:33:31 +0000 [thread overview]
Message-ID: <MW5PR11MB5908315F5E72DBE3520070E6A91B2@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Zi9R3Q54/uKm75tf@tucnak>
Committed to trunk, thanks Kito.
Backported to releases/gcc-14, thanks Jakub.
Pan
-----Original Message-----
From: Jakub Jelinek <jakub@redhat.com>
Sent: Monday, April 29, 2024 3:53 PM
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Li, Pan2 <pan2.li@intel.com>; Jeff Law <jeffreyalaw@gmail.com>; gcc-patches@gcc.gnu.org; juzhe.zhong@rivai.ai
Subject: Re: [PATCH v2] RISC-V: Fix ICE for legitimize move on subreg const_poly_int [PR114885]
On Mon, Apr 29, 2024 at 03:47:05PM +0800, Kito Cheng wrote:
> Hi Jakub:
>
> Is this OK for GCC 14 branch? it's fix ICE on valid code, thanks :)
Ok.
Jakub
prev parent reply other threads:[~2024-04-29 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 3:53 [PATCH v1] RISC-V: Fix ICE for legitimize move on subreg const_poly_move pan2.li
2024-04-28 3:55 ` juzhe.zhong
2024-04-29 6:37 ` Kito Cheng
2024-04-29 7:41 ` Li, Pan2
2024-04-29 7:40 ` [PATCH v2] RISC-V: Fix ICE for legitimize move on subreg const_poly_int [PR114885] pan2.li
2024-04-29 7:47 ` Kito Cheng
2024-04-29 7:53 ` Jakub Jelinek
2024-04-29 8:33 ` Li, Pan2 [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=MW5PR11MB5908315F5E72DBE3520070E6A91B2@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
/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).