public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	"Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Peter Bergner <bergner@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Move V2DI vec_neg under power8-vector [PR105271]
Date: Tue, 26 Apr 2022 17:16:18 +0200	[thread overview]
Message-ID: <YmgMwm7tw+iCCXIz@tucnak> (raw)
In-Reply-To: <57f5d965-7aea-3e0d-501c-7f8a8b670eab@linux.ibm.com>

Hi!

On Fri, Apr 15, 2022 at 04:08:15PM +0800, Kewen.Lin via Gcc-patches wrote:
> As PR105271 shows, __builtin_altivec_neg_v2di requires option
> -mpower8-vector as its pattern expansion relies on subv2di which
> has guard VECTOR_UNIT_P8_VECTOR_P (V2DImode).  This fix is to move
> the related lines for __builtin_altivec_neg_v2di to the section
> of stanza power8-vector.
> 
> Bootstrapped and regtested on powerpc64-linux-gnu P8 and
> powerpc64le-linux-gnu P9 and P10.
> 
> Is it ok for trunk?
> 
> BR,
> Kewen
> -----
> 	PR target/105271
> 
> gcc/ChangeLog:
> 
> 	* config/rs6000/rs6000-builtins.def (NEG_V2DI): Move to [power8-vector]
> 	stanza.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.target/powerpc/pr105271.c: New test.

I'd like to ping this patch, one of the last few remaining P1s we have for
GCC 12.

Thanks.

	Jakub


  reply	other threads:[~2022-04-26 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  8:08 Kewen.Lin
2022-04-26 15:16 ` Jakub Jelinek [this message]
2022-04-26 15:25   ` Segher Boessenkool
2022-04-27  1:49     ` Kewen.Lin

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=YmgMwm7tw+iCCXIz@tucnak \
    --to=jakub@redhat.com \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.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).