public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: "Andre Vieira \(lists\)" <andre.simoesdiasvieira@arm.com>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Subject: Re: [PATCH] aarch64: Add aarch64*-*-* to the list of vect_long_long targets
Date: Tue, 24 Jan 2023 17:23:12 +0000	[thread overview]
Message-ID: <mptbkmnoni7.fsf@arm.com> (raw)
In-Reply-To: <12259c76-b704-86eb-c93e-b0a92b0db269@arm.com> (Andre Vieira's message of "Tue, 24 Jan 2023 16:52:51 +0000")

"Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com> writes:
> Hi,
>
> This patch adds aarch64 to the list of vect_long_long targets. 
> Regression tested on aarch64-none-linux-gnu.
>
> OK for trunk?
>
> gcc/testsuite/ChangeLog:
>
> 	* lib/target-supports.exp (check_effective_target_vect_long_long): Add
> 	aarch64 to list of targets supporting long long vectorization.

OK, thanks.

Richard

> diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
> index c0694af233818b5923919b33c5ae6f9d1955d118..227e3004077a374317ae20c323c03a9b2ce15292 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -7125,7 +7125,8 @@ proc check_effective_target_vect_long_long { } {
>  		 && [check_effective_target_s390_vx])
>  	     || ([istarget powerpc*-*-*]
>  		 && ![istarget powerpc-*-linux*paired*]
> -		 && [check_effective_target_has_arch_pwr8]) }}]
> +		 && [check_effective_target_has_arch_pwr8])
> +	     || [istarget aarch64*-*-*] }}]
>  }
>  
>  

      reply	other threads:[~2023-01-24 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 16:52 Andre Vieira (lists)
2023-01-24 17:23 ` Richard Sandiford [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=mptbkmnoni7.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=Kyrylo.Tkachov@arm.com \
    --cc=andre.simoesdiasvieira@arm.com \
    --cc=gcc-patches@gcc.gnu.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).