public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Andre Vieira <andre.simoesdiasvieira@arm.com>, gcc-patches@gcc.gnu.org
Cc: stam.markianos-wright@arm.com
Subject: Re: [PATCH v6 2/5] arm: Annotate instructions with mve_safe_imp_xlane_pred
Date: Fri, 1 Mar 2024 15:35:06 +0000	[thread overview]
Message-ID: <4786172f-7d24-43ae-9af2-0ec41adad676@arm.com> (raw)
In-Reply-To: <20240227135647.30404-3-andre.simoesdiasvieira@arm.com>

On 27/02/2024 13:56, Andre Vieira wrote:
> 
> This patch annotates some MVE across lane instructions with a new attribute.
> We use this attribute to let the compiler know that these instructions can be
> safely implicitly predicated when tail predicating if their operands are
> guaranteed to have zeroed tail predicated lanes.  These instructions were
> selected because having the value 0 in those lanes or 'tail-predicating' those
> lanes have the same effect.
> 
> gcc/ChangeLog:
> 
> 	* config/arm/arm.md (mve_safe_imp_xlane_pred): New attribute.
> 	* config/arm/iterators.md (mve_vmaxmin_safe_imp): New iterator
> 	attribute.
> 	* config/arm/mve.md (vaddvq_s, vaddvq_u, vaddlvq_s, vaddlvq_u,
> 	vaddvaq_s, vaddvaq_u, vmaxavq_s, vmaxvq_u, vmladavq_s, vmladavq_u,
> 	vmladavxq_s, vmlsdavq_s, vmlsdavxq_s, vaddlvaq_s, vaddlvaq_u,
> 	vmlaldavq_u, vmlaldavq_s, vmlaldavq_u, vmlaldavxq_s, vmlsldavq_s,
> 	vmlsldavxq_s, vrmlaldavhq_u, vrmlaldavhq_s, vrmlaldavhxq_s,
> 	vrmlsldavhq_s, vrmlsldavhxq_s, vrmlaldavhaq_s, vrmlaldavhaq_u,
> 	vrmlaldavhaxq_s, vrmlsldavhaq_s, vrmlsldavhaxq_s, vabavq_s, vabavq_u,
> 	vmladavaq_u, vmladavaq_s, vmladavaxq_s, vmlsdavaq_s, vmlsdavaxq_s,
> 	vmlaldavaq_s, vmlaldavaq_u, vmlaldavaxq_s, vmlsldavaq_s,
> 	vmlsldavaxq_s): Added mve_safe_imp_xlane_pred.
> ---
>  gcc/config/arm/arm.md       |  6 ++++++
>  gcc/config/arm/iterators.md |  8 ++++++++
>  gcc/config/arm/mve.md       | 12 ++++++++++++
>  3 files changed, 26 insertions(+)
> 

OK

R.

  reply	other threads:[~2024-03-01 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 13:56 [PATCH v5 0/5] arm: Add support for MVE Tail-Predicated Low Overhead Loops Andre Vieira
2024-02-27 13:56 ` [PATCH v6 1/5] arm: Add define_attr to to create a mapping between MVE predicated and unpredicated insns Andre Vieira
2024-03-01 15:34   ` Richard Earnshaw (lists)
2024-02-27 13:56 ` [PATCH v6 2/5] arm: Annotate instructions with mve_safe_imp_xlane_pred Andre Vieira
2024-03-01 15:35   ` Richard Earnshaw (lists) [this message]
2024-02-27 13:56 ` [PATCH v6 3/5] arm: Fix a wrong attribute use and remove unused unspecs and iterators Andre Vieira
2024-03-01 15:35   ` Richard Earnshaw (lists)
2024-02-27 13:56 ` [PATCH v6 4/5] doloop: Add support for predicated vectorized loops Andre Vieira
2024-03-01 15:37   ` Richard Earnshaw (lists)
2024-02-27 13:56 ` [PATCH v6 5/5] arm: Add support for MVE Tail-Predicated Low Overhead Loops Andre Vieira
2024-03-01 15:39   ` Richard Earnshaw (lists)

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=4786172f-7d24-43ae-9af2-0ec41adad676@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=andre.simoesdiasvieira@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stam.markianos-wright@arm.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).