From: Richard Sandiford <richard.sandiford@arm.com>
To: Andrew Pinski <quic_apinski@quicinc.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix vect_long_mult for aarch64 [PR109705]
Date: Wed, 24 Jan 2024 18:12:44 +0000 [thread overview]
Message-ID: <mptttn2fvmr.fsf@arm.com> (raw)
In-Reply-To: <20240124173646.4025318-1-quic_apinski@quicinc.com> (Andrew Pinski's message of "Wed, 24 Jan 2024 09:36:46 -0800")
Andrew Pinski <quic_apinski@quicinc.com> writes:
> On aarch64, vectorization of `long` multiply can be done if SVE is enabled
> or if long is 32bit (ILP32). It can also be done for constants too but there
> is no effective target test for that just yet.
>
> Build and tested on aarch64-linux-gnu with no regressions (also tested with SVE enabled).
>
> gcc/testsuite/ChangeLog:
>
> * lib/target-supports.exp (check_effective_target_vect_long_mult):
> Fix aarch64*-*-* checks.
OK, thanks!
Richard
> Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
> ---
> gcc/testsuite/lib/target-supports.exp | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
> index 9ca8355b3e1..178d1a73064 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -9090,7 +9090,9 @@ proc check_effective_target_vect_long_mult { } {
> && [check_effective_target_has_arch_pwr10])
> || [is-effective-target arm_neon]
> || ([istarget sparc*-*-*] && [check_effective_target_ilp32])
> - || [istarget aarch64*-*-*]
> + || ([istarget aarch64*-*-*]
> + && ([check_effective_target_ilp32]
> + || check_effective_target_aarch64_sve]))
> || ([istarget mips*-*-*]
> && [et-is-effective-target mips_msa])
> || ([istarget riscv*-*-*]
next prev parent reply other threads:[~2024-01-24 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 17:36 Andrew Pinski
2024-01-24 18:12 ` Richard Sandiford [this message]
2024-01-25 0:38 ` H.J. Lu
2024-01-25 0:41 ` Andrew Pinski
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=mptttn2fvmr.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=quic_apinski@quicinc.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).