From: Christophe Lyon <christophe.lyon.oss@gmail.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3 00/15] ARM/MVE use vectors of boolean for predicates
Date: Wed, 26 Jan 2022 09:40:55 +0100 [thread overview]
Message-ID: <CAKhMtSJ6K-0NobT_asgDAfv0P51nDuOphreH8UJePN1+WWrUqg@mail.gmail.com> (raw)
In-Reply-To: <PAXPR08MB69261FBCF5D72C8FBEE5372793549@PAXPR08MB6926.eurprd08.prod.outlook.com>
Ping?
As discussed elsewhere with André, I'll drop patch #15 from this series,
since his patch
is a better fix.
Since v2 of this series had been approved, I think only patches 4,7,8,9,12
and 13 need
proper review.
Thanks,
Christophe
On Fri, Jan 14, 2022 at 3:22 PM Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
wrote:
> Hi Christophe, Richard,
>
> > -----Original Message-----
> > From: Gcc-patches <gcc-patches-
> > bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On Behalf Of Richard
> > Biener via Gcc-patches
> > Sent: Friday, January 14, 2022 1:33 PM
> > To: Christophe Lyon <christophe.lyon.oss@gmail.com>
> > Cc: GCC Patches <gcc-patches@gcc.gnu.org>
> > Subject: Re: [PATCH v3 00/15] ARM/MVE use vectors of boolean for
> > predicates
> >
> > On Fri, Jan 14, 2022 at 2:18 PM Christophe Lyon via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> > >
> > > Hi,
> > >
> > > I hadn't realized we are moving to stage 4 this week-end :-(
> > >
> > > The PRs I'm fixing are P3, but without these fixes MVE support is badly
> > > broken, so I think I would be really good to fix that before the buggy
> > > version becomes part of an actual release.
> > > Anyway I posted v1 of the patches during stage1, so it should still be
> OK
> > > if they are accepted as-is ?
> >
> > In the end it's up to the target maintainers to weight the risk of
> breakage
> > vs. the risk of not usefulness ;) But stage3 is where the "was posted
> > during stage1"
> > rule can easily apply - at some point we have to stop with such general
> ruling.
> >
>
> Thanks, that's in line with my interpretation.
> These patches resolve some nasty brokenness in the MVE support that I'm
> keen to see fixed and from what I can tell the patches shouldn't have a
> large effect on non-MVE code.
> So the risk vs reward balance for the arm port as a whole looks good to me.
> Andre has kindly agreed to help review the patches and I'll also try to
> get to them today and next week so that we can get them in early stage4.
>
> Thanks,
> Kyrill
>
> > Richard.
> >
> > > Thanks,
> > >
> > > Christophe
> > >
> > > On Thu, Jan 13, 2022 at 3:58 PM Christophe Lyon via Gcc-patches <
> > > gcc-patches@gcc.gnu.org> wrote:
> > >
> > > >
> > > > This is v3 of this patch series, fixing issues I discovered before
> > > > committing v2 (which had been approved).
> > > >
> > > > Thanks a lot to Richard Sandiford for his help.
> > > >
> > > > The changes v2 -> v3 are:
> > > >
> > > > Patch 4: Fix arm_hard_regno_nregs and CLASS_MAX_NREGS to support
> > VPR.
> > > >
> > > > Patch 7: Changes to the underlying representation of vectors of
> > > > booleans to account for the different expectations between
> AArch64/SVE
> > > > and Arm/MVE.
> > > >
> > > > Patch 8: Re-use and extend existing thumb2_movhi* patterns instead of
> > > > duplicating them in mve_mov<mode>. This requires the introduction of
> a
> > > > new constraint to match a constant vector of booleans. Add a new RTL
> > > > test.
> > > >
> > > > Patch 9: Introduce check_effective_target_arm_mve and skip
> > > > gcc.dg/signbit-2.c, because with MVE there is no fallback
> architecture
> > > > unlike SVE or AVX512.
> > > >
> > > > Patch 12: Update less load/store MVE builtins
> > > > (mve_vldrdq_gather_base_z_<supf>v2di,
> > > > mve_vldrdq_gather_offset_z_<supf>v2di,
> > > > mve_vldrdq_gather_shifted_offset_z_<supf>v2di,
> > > > mve_vstrdq_scatter_base_p_<supf>v2di,
> > > > mve_vstrdq_scatter_offset_p_<supf>v2di,
> > > > mve_vstrdq_scatter_offset_p_<supf>v2di_insn,
> > > > mve_vstrdq_scatter_shifted_offset_p_<supf>v2di,
> > > > mve_vstrdq_scatter_shifted_offset_p_<supf>v2di_insn,
> > > > mve_vstrdq_scatter_base_wb_p_<supf>v2di,
> > > > mve_vldrdq_gather_base_wb_z_<supf>v2di,
> > > > mve_vldrdq_gather_base_nowb_z_<supf>v2di,
> > > > mve_vldrdq_gather_base_wb_z_<supf>v2di_insn) for which we keep HI
> > mode
> > > > for vpr_register_operand.
> > > >
> > > > Patch 13: No need to update
> > > > gcc.target/arm/acle/cde-mve-full-assembly.c anymore since we re-use
> > > > the mov pattern that emits '@ movhi' in the assembly.
> > > >
> > > > Patch 15: This is a new patch to fix a problem I noticed during this
> > > > v2->v3 update.
> > > >
> > > >
> > > >
> > > > I'll squash patch 2 with patch 9 and patch 3 with patch 8.
> > > >
> > > > Original text:
> > > >
> > > > This patch series addresses PR 100757 and 101325 by representing
> > > > vectors of predicates (MVE VPR.P0 register) as vectors of booleans
> > > > rather than using HImode.
> > > >
> > > > As this implies a lot of mostly mechanical changes, I have tried to
> > > > split the patches in a way that should help reviewers, but the split
> > > > is a bit artificial.
> > > >
> > > > Patches 1-3 add new tests.
> > > >
> > > > Patches 4-6 are small independent improvements.
> > > >
> > > > Patch 7 implements the predicate qualifier, but does not change any
> > > > builtin yet.
> > > >
> > > > Patch 8 is the first of the two main patches, and uses the new
> > > > qualifier to describe the vcmp and vpsel builtins that are useful for
> > > > auto-vectorization of comparisons.
> > > >
> > > > Patch 9 is the second main patch, which fixes the vcond_mask
> expander.
> > > >
> > > > Patches 10-13 convert almost all the remaining builtins with HI
> > > > operands to use the predicate qualifier. After these, there are
> still
> > > > a few builtins with HI operands left, about which I am not sure:
> vctp,
> > > > vpnot, load-gather and store-scatter with v2di operands. In fact,
> > > > patches 11/12 update some STR/LDR qualifiers in a way that breaks
> > > > these v2di builtins although existing tests still pass.
> > > >
> > > > Christophe Lyon (15):
> > > > arm: Add new tests for comparison vectorization with Neon and MVE
> > > > arm: Add tests for PR target/100757
> > > > arm: Add tests for PR target/101325
> > > > arm: Add GENERAL_AND_VPR_REGS regclass
> > > > arm: Add support for VPR_REG in arm_class_likely_spilled_p
> > > > arm: Fix mve_vmvnq_n_<supf><mode> argument mode
> > > > arm: Implement MVE predicates as vectors of booleans
> > > > arm: Implement auto-vectorized MVE comparisons with vectors of
> > boolean
> > > > predicates
> > > > arm: Fix vcond_mask expander for MVE (PR target/100757)
> > > > arm: Convert remaining MVE vcmp builtins to predicate qualifiers
> > > > arm: Convert more MVE builtins to predicate qualifiers
> > > > arm: Convert more load/store MVE builtins to predicate qualifiers
> > > > arm: Convert more MVE/CDE builtins to predicate qualifiers
> > > > arm: Add VPR_REG to ALL_REGS
> > > > arm: Fix constraint check for V8HI in mve_vector_mem_operand
> > > >
> > > > gcc/config/aarch64/aarch64-modes.def | 8 +-
> > > > gcc/config/arm/arm-builtins.c | 224 +++--
> > > > gcc/config/arm/arm-builtins.h | 4 +-
> > > > gcc/config/arm/arm-modes.def | 8 +
> > > > gcc/config/arm/arm-protos.h | 4 +-
> > > > gcc/config/arm/arm-simd-builtin-types.def | 4 +
> > > > gcc/config/arm/arm.c | 169 ++--
> > > > gcc/config/arm/arm.h | 9 +-
> > > > gcc/config/arm/arm_mve_builtins.def | 746 ++++++++--------
> > > > gcc/config/arm/constraints.md | 6 +
> > > > gcc/config/arm/iterators.md | 6 +
> > > > gcc/config/arm/mve.md | 795
> ++++++++++--------
> > > > gcc/config/arm/neon.md | 39 +
> > > > gcc/config/arm/vec-common.md | 52 --
> > > > gcc/config/arm/vfp.md | 34 +-
> > > > gcc/doc/sourcebuild.texi | 4 +
> > > > gcc/emit-rtl.c | 20 +-
> > > > gcc/genmodes.c | 81 +-
> > > > gcc/machmode.def | 2 +-
> > > > gcc/rtx-vector-builder.c | 4 +-
> > > > gcc/simplify-rtx.c | 34 +-
> > > > gcc/testsuite/gcc.dg/signbit-2.c | 1 +
> > > > .../gcc.target/arm/simd/mve-vcmp-f32-2.c | 32 +
> > > > .../gcc.target/arm/simd/neon-compare-1.c | 78 ++
> > > > .../gcc.target/arm/simd/neon-compare-2.c | 13 +
> > > > .../gcc.target/arm/simd/neon-compare-3.c | 14 +
> > > > .../arm/simd/neon-compare-scalar-1.c | 57 ++
> > > > .../gcc.target/arm/simd/neon-vcmp-f16.c | 12 +
> > > > .../gcc.target/arm/simd/neon-vcmp-f32-2.c | 15 +
> > > > .../gcc.target/arm/simd/neon-vcmp-f32-3.c | 12 +
> > > > .../gcc.target/arm/simd/neon-vcmp-f32.c | 12 +
> > > > gcc/testsuite/gcc.target/arm/simd/neon-vcmp.c | 22 +
> > > > .../gcc.target/arm/simd/pr100757-2.c | 20 +
> > > > .../gcc.target/arm/simd/pr100757-3.c | 20 +
> > > > .../gcc.target/arm/simd/pr100757-4.c | 19 +
> > > > gcc/testsuite/gcc.target/arm/simd/pr100757.c | 19 +
> > > > .../gcc.target/arm/simd/pr101325-2.c | 19 +
> > > > gcc/testsuite/gcc.target/arm/simd/pr101325.c | 14 +
> > > > gcc/testsuite/lib/target-supports.exp | 15 +-
> > > > gcc/varasm.c | 7 +-
> > > > 40 files changed, 1635 insertions(+), 1019 deletions(-)
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/mve-vcmp-f32-
> > 2.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-compare-
> > 1.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-compare-
> > 2.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-compare-
> > 3.c
> > > > create mode 100644
> > > > gcc/testsuite/gcc.target/arm/simd/neon-compare-scalar-1.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-vcmp-f16.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-vcmp-f32-
> > 2.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-vcmp-f32-
> > 3.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-vcmp-f32.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/neon-vcmp.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr100757-2.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr100757-3.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr100757-4.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr100757.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr101325-2.c
> > > > create mode 100644 gcc/testsuite/gcc.target/arm/simd/pr101325.c
> > > >
> > > > --
> > > > 2.25.1
> > > >
> > > >
>
prev parent reply other threads:[~2022-01-26 8:41 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:56 Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 01/15] arm: Add new tests for comparison vectorization with Neon and MVE Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 02/15] arm: Add tests for PR target/100757 Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 03/15] arm: Add tests for PR target/101325 Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 04/15] arm: Add GENERAL_AND_VPR_REGS regclass Christophe Lyon
2022-01-19 18:17 ` Andre Vieira (lists)
2022-01-20 9:14 ` Christophe Lyon
2022-01-20 9:43 ` Andre Vieira (lists)
2022-01-20 10:40 ` Richard Sandiford
2022-01-20 10:45 ` Andre Vieira (lists)
2022-01-27 16:21 ` Kyrylo Tkachov
2022-01-13 14:56 ` [PATCH v3 05/15] arm: Add support for VPR_REG in arm_class_likely_spilled_p Christophe Lyon
2022-01-19 18:25 ` Andre Vieira (lists)
2022-01-20 9:20 ` Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 06/15] arm: Fix mve_vmvnq_n_<supf><mode> argument mode Christophe Lyon
2022-01-19 19:03 ` Andre Vieira (lists)
2022-01-20 9:23 ` Christophe Lyon
2022-01-20 9:38 ` Andre Simoes Dias Vieira
2022-01-20 9:44 ` Christophe Lyon
2022-01-20 10:45 ` Richard Sandiford
2022-01-20 11:06 ` Andre Vieira (lists)
2022-01-13 14:56 ` [PATCH v3 07/15] arm: Implement MVE predicates as vectors of booleans Christophe Lyon
2022-01-21 11:20 ` Andre Vieira (lists)
2022-01-21 22:30 ` Christophe Lyon
2022-01-27 16:28 ` Kyrylo Tkachov
2022-01-27 18:10 ` Christophe Lyon
2022-01-31 18:01 ` Richard Sandiford
2022-01-31 22:57 ` Christophe Lyon
2022-02-01 3:42 ` Richard Sandiford
2022-02-02 16:51 ` Christophe Lyon
2022-02-04 9:42 ` Richard Sandiford
2022-02-04 9:54 ` Richard Sandiford
2022-02-17 15:39 ` Christophe Lyon
2022-02-21 18:18 ` Richard Sandiford
2022-01-13 14:56 ` [PATCH v3 08/15] arm: Implement auto-vectorized MVE comparisons with vectors of boolean predicates Christophe Lyon
2022-01-27 16:37 ` Kyrylo Tkachov
2022-01-13 14:56 ` [PATCH v3 09/15] arm: Fix vcond_mask expander for MVE (PR target/100757) Christophe Lyon
2022-01-27 16:55 ` Kyrylo Tkachov
2022-01-13 14:56 ` [PATCH v3 10/15] arm: Convert remaining MVE vcmp builtins to predicate qualifiers Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 11/15] arm: Convert more MVE " Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 12/15] arm: Convert more load/store " Christophe Lyon
2022-01-27 16:56 ` Kyrylo Tkachov
2022-01-13 14:56 ` [PATCH v3 13/15] arm: Convert more MVE/CDE " Christophe Lyon
2022-01-27 16:56 ` Kyrylo Tkachov
2022-01-13 14:56 ` [PATCH v3 14/15] arm: Add VPR_REG to ALL_REGS Christophe Lyon
2022-01-13 14:56 ` [PATCH v3 15/15] arm: Fix constraint check for V8HI in mve_vector_mem_operand Christophe Lyon
2022-01-14 17:03 ` [arm] MVE: Relax addressing modes for full loads and stores Andre Vieira (lists)
2022-01-17 7:48 ` Christophe Lyon
2022-03-07 14:16 ` Andre Vieira (lists)
2022-03-07 16:14 ` Kyrylo Tkachov
2022-01-14 13:18 ` [PATCH v3 00/15] ARM/MVE use vectors of boolean for predicates Christophe Lyon
2022-01-14 13:33 ` Richard Biener
2022-01-14 14:22 ` Kyrylo Tkachov
2022-01-26 8:40 ` Christophe Lyon [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=CAKhMtSJ6K-0NobT_asgDAfv0P51nDuOphreH8UJePN1+WWrUqg@mail.gmail.com \
--to=christophe.lyon.oss@gmail.com \
--cc=Kyrylo.Tkachov@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).