public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@linux.ibm.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/3] s390: Recognize further vpdi and vmr{l,h} pattern
Date: Thu, 9 Nov 2023 09:27:18 +0100	[thread overview]
Message-ID: <31069b16-1e2e-721a-d979-1d2627bf1254@linux.ibm.com> (raw)
In-Reply-To: <20231109082211.2505-1-stefansf@linux.ibm.com>

On 11/9/23 09:22, Stefan Schulze Frielinghaus wrote:
> Deal with cases where vpdi and vmr{l,h} are still applicable if the
> operands of those instructions are swapped.  For example, currently for
> 
> V2DI foo (V2DI x)
> {
>   return (V2DI) {x[1], x[0]};
> }
> 
> the assembler sequence
> 
> vlgvg   %r1,%v24,1
> vzero   %v0
> vlvgg   %v0,%r1,0
> vmrhg   %v24,%v0,%v24
> 
> is emitted.  With this patch a single vpdi is emitted.
> 
> Extensive tests are included in a subsequent patch of this series where
> more cases are covered.
> 
> Bootstrapped and regtested on s390.  Ok for mainline?
> 
> gcc/ChangeLog:
> 
> 	* config/s390/s390.cc (expand_perm_with_merge): Deal with cases
> 	where vmr{l,h} are still applicable if the operands are swapped.
> 	(expand_perm_with_vpdi): Likewise for vpdi.

Ok, Thanks!

Andreas


      parent reply	other threads:[~2023-11-09  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09  8:22 Stefan Schulze Frielinghaus
2023-11-09  8:22 ` [PATCH 2/3] s390: Add expand_perm_reverse_elements Stefan Schulze Frielinghaus
2023-11-09  8:27   ` Andreas Krebbel
2023-11-09  8:22 ` [PATCH 3/3] s390: Revise vector reverse elements Stefan Schulze Frielinghaus
2023-11-09  8:27   ` Andreas Krebbel
2023-11-09  8:27 ` Andreas Krebbel [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=31069b16-1e2e-721a-d979-1d2627bf1254@linux.ibm.com \
    --to=krebbel@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stefansf@linux.ibm.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).