From: Peter Bergner <bergner@linux.ibm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
"Kewen.Lin" <linkw@linux.ibm.com>,
Chip Kerchner <Chip.Kerchner@ibm.com>
Subject: Re: [PATCH] rs6000: Don't ICE when compiling the __builtin_vec_xst_trunc built-in [PR109178]
Date: Fri, 17 Mar 2023 21:30:59 -0500 [thread overview]
Message-ID: <f47d4b0d-3f59-5efc-be01-f3bd5a809890@linux.ibm.com> (raw)
In-Reply-To: <eddcba92-3f32-976e-5fdf-26120376f824@linux.ibm.com>
On 3/17/23 7:17 PM, Peter Bergner wrote:
> On 3/17/23 5:35 PM, Peter Bergner wrote:
>> When we expand the __builtin_vec_xst_trunc built-in, we use the wrong mode
>> for the MEM operand which causes an unrecognizable insn ICE. The solution
>> is to use the correct TMODE mode.
>>
>> Is this ok for trunk and gcc12 assuming my bootstraps and regtests show
>> no regressions?
>
> The trunk bootstrap and regtests were clean. I'm still waiting on the
> backport testing to finish.
...and the gcc12 backported bootstrap and regtest were clean too.
Peter
next prev parent reply other threads:[~2023-03-18 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 22:35 Peter Bergner
2023-03-18 0:17 ` Peter Bergner
2023-03-18 2:30 ` Peter Bergner [this message]
2023-03-20 3:20 ` Kewen.Lin
2023-03-21 2:24 ` Peter Bergner
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=f47d4b0d-3f59-5efc-be01-f3bd5a809890@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=Chip.Kerchner@ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.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).