From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com,
richard.earnshaw@arm.com, kyrylo.tkachov@arm.com
Subject: Re: [PATCH 3/6] arm: [MVE intrinsics] Add support for contiguous loads and stores
Date: Thu, 23 Nov 2023 16:57:56 +0100 [thread overview]
Message-ID: <CAPS5khb9B1cdSbtoLWcRF7_ub0RYU=N2pYJcdsBR1F+qaZY9YA@mail.gmail.com> (raw)
In-Reply-To: <20231123132936.GH21972@lug-owl.de>
Hi!
On Thu, 23 Nov 2023 at 14:29, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>
> On Thu, 2023-11-16 15:26:14 +0000, Christophe Lyon <christophe.lyon@linaro.org> wrote:
> > diff --git a/gcc/config/arm/arm-mve-builtins-functions.h b/gcc/config/arm/arm-mve-builtins-functions.h
> > index eba1f071af0..6d234a2dd7c 100644
> > --- a/gcc/config/arm/arm-mve-builtins-functions.h
> > +++ b/gcc/config/arm/arm-mve-builtins-functions.h
> > @@ -966,6 +966,62 @@ public:
> [...]
>
> > +class full_width_access : public multi_vector_function
> > +{
> > +public:
> > + CONSTEXPR full_width_access (unsigned int vectors_per_tuple = 1)
> > + : multi_vector_function (vectors_per_tuple) {}
> > +
> > + tree
> > + memory_scalar_type (const function_instance &fi) const override
> > + {
> > + return fi.scalar_type (0);
> > + }
> > +
> > + machine_mode
> > + memory_vector_mode (const function_instance &fi) const override
> > + {
> > + machine_mode mode = fi.vector_mode (0);
> > + /* Vectors of floating-point are managed in memory as vectors of
> > + integers. */
> > + switch (mode)
> > + {
> > + case E_V4SFmode:
> > + mode = E_V4SImode;
> > + break;
> > + case E_V8HFmode:
> > + mode = E_V8HImode;
> > + break;
> > + }
>
> This introduces warnings about many enum values not being handled, so
> a default would be good I think. (I do automated builds with
> --enable-werror-always, see eg.
> http://toolchain.lug-owl.de/laminar/log/gcc-arm-eabi/48)
>
Ha right, thanks for catching this.
Fixed by commit b9dbdefac626ba20222ca534b58f7e493d713b9a
Christophe
> MfG, JBG
>
> --
next prev parent reply other threads:[~2023-11-23 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 15:26 [PATCH 1/6] arm: Fix arm_simd_types and MVE scalar_types Christophe Lyon
2023-11-16 15:26 ` [PATCH 2/6] arm: [MVE intrinsics] Add support for void and load/store pointers as argument types Christophe Lyon
2023-11-16 16:47 ` Kyrylo Tkachov
2023-11-16 15:26 ` [PATCH 3/6] arm: [MVE intrinsics] Add support for contiguous loads and stores Christophe Lyon
2023-11-16 16:48 ` Kyrylo Tkachov
2023-11-23 13:29 ` Jan-Benedict Glaw
2023-11-23 15:57 ` Christophe Lyon [this message]
2023-11-16 15:26 ` [PATCH 4/6] arm: [MVE intrinsics] add load and store shapes Christophe Lyon
2023-11-16 16:49 ` Kyrylo Tkachov
2023-11-16 15:26 ` [PATCH 5/6] arm: [MVE intrinsics] fix vst1 tests Christophe Lyon
2023-11-16 15:30 ` Kyrylo Tkachov
2023-11-16 15:37 ` Christophe Lyon
2023-11-16 15:26 ` [PATCH 6/6] arm: [MVE intrinsics] rework vldq1 vst1q Christophe Lyon
2023-11-16 16:49 ` Kyrylo Tkachov
2023-11-16 16:46 ` [PATCH 1/6] arm: Fix arm_simd_types and MVE scalar_types 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='CAPS5khb9B1cdSbtoLWcRF7_ub0RYU=N2pYJcdsBR1F+qaZY9YA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=kyrylo.tkachov@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@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).