From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR 107674]
Date: Tue, 24 Jan 2023 13:48:54 +0000 [thread overview]
Message-ID: <f136c96b-cda5-7d1d-b520-8a457045a155@arm.com> (raw)
In-Reply-To: <ae05c3e4-c4a5-69a6-b61b-1d22b63ec9cf@arm.com>
I meant bootstrapped on aarch64-none-linux-gnu and not none-eabi.
On 24/01/2023 13:40, Andre Vieira (lists) via Gcc-patches wrote:
> Hi,
>
> The ACLE defines mve_pred16_t as an unsigned short. This patch makes
> sure GCC treats the predicate as an unsigned type, rather than signed.
>
> Bootstrapped on aarch64-none-eabi and regression tested on arm-none-eabi
> and armeb-none-eabi for armv8.1-m.main+mve.fp.
>
> OK for trunk?
>
> gcc/ChangeLog:
>
> PR target/107674
> * config/arm/arm-builtins.cc (arm_simd_builtin_type): Rewrite to use
> new qualifiers parameter and use unsigned short type for MVE
> predicate.
> (arm_init_builtin): Call arm_simd_builtin_type with qualifiers
> parameter.
> (arm_init_crypto_builtins): Likewise.
>
> gcc/testsuite/ChangeLog:
>
> PR target/107674
> * gcc.target/arm/mve/mve_vpt.c: New test.
next prev parent reply other threads:[~2023-01-24 13:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 13:31 [PATCH 0/3] arm: Fix regressions around MVE predicate codegen Andre Vieira (lists)
2023-01-24 13:40 ` [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR 107674] Andre Vieira (lists)
2023-01-24 13:48 ` Andre Vieira (lists) [this message]
2023-01-26 15:02 ` Kyrylo Tkachov
2023-01-26 15:03 ` Kyrylo Tkachov
2023-01-27 9:54 ` Andre Vieira (lists)
2023-01-27 9:56 ` Kyrylo Tkachov
2023-01-30 16:38 ` Andre Vieira (lists)
2023-01-30 16:40 ` Kyrylo Tkachov
2023-01-24 13:54 ` [PATCH 2/3] arm: Remove unnecessary zero-extending of MVE predicates before use " Andre Vieira (lists)
2023-01-26 15:06 ` Kyrylo Tkachov
2023-01-27 9:58 ` Andre Vieira (lists)
2023-01-27 9:59 ` Kyrylo Tkachov
2023-01-30 16:41 ` Andre Vieira (lists)
2023-01-30 23:17 ` Richard Sandiford
2023-01-31 6:15 ` Richard Sandiford
2023-01-24 13:56 ` [PATCH 3/3] arm: Fix MVE predicates synthesis [PR 108443] Andre Vieira (lists)
2023-01-25 17:40 ` Andre Vieira (lists)
2023-01-31 9:53 ` Kyrylo Tkachov
2023-01-31 11:38 ` Andre Vieira (lists)
2023-01-31 16:44 ` Kyrylo Tkachov
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=f136c96b-cda5-7d1d-b520-8a457045a155@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@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).