public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
	Richard Biener <rguenther@suse.de>,
		Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: [PATCH][armeb] PR 91060 gcc.c-torture/execute/scal-to-vec1.c fails since r272843
Date: Mon, 08 Jul 2019 09:16:00 -0000	[thread overview]
Message-ID: <CAKdteOaW8nuGAB4EM3e5MZXJuC5thzfAUdDeZmHWrRO+v++tbA@mail.gmail.com> (raw)
In-Reply-To: <b2d5fe36-52c6-fc62-d0b1-7937ba6f25a0@foss.arm.com>

On Mon, 8 Jul 2019 at 11:06, Kyrill Tkachov <kyrylo.tkachov@foss.arm.com> wrote:
>
> Hi Christophe
>
> On 7/8/19 10:01 AM, Christophe Lyon wrote:
> > Hi,
> >
> > This patch fixes PR 91060 where the lane ordering was no longer the
> > right one (GCC's vs architecture's).
> >
> > OK?
> >
> > Thanks to both Richards for most of the debugging!
>
> Thank you to all for tracking this down.
>
> >
> > Christophe
>
>
> pr91060.patch.txt
>
> diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
> index 820502a..4c7b5a8 100644
> --- a/gcc/config/arm/arm.c
> +++ b/gcc/config/arm/arm.c
> @@ -12471,7 +12471,7 @@ neon_expand_vector_init (rtx target, rtx vals)
>     if (n_var == 1)
>       {
>         rtx copy = copy_rtx (vals);
> -      rtx index = GEN_INT (one_var);
> +      rtx index = GEN_INT (1 << one_var);
>
>         /* Load constant part of vector, substitute neighboring value for
>          varying element.  */
> @@ -12483,31 +12483,31 @@ neon_expand_vector_init (rtx target, rtx vals)
>         switch (mode)
>         {
>         case E_V8QImode:
> -         emit_insn (gen_neon_vset_lanev8qi (target, x, target, index));
> +         emit_insn (gen_vec_setv8qi_internal (target, x, index, target));
>           break;
>         case E_V16QImode:
> -         emit_insn (gen_neon_vset_lanev16qi (target, x, target, index));
> +         emit_insn (gen_vec_setv16qi_internal (target, x, index, target));
>           break;
>         case E_V4HImode:
> -         emit_insn (gen_neon_vset_lanev4hi (target, x, target, index));
> +         emit_insn (gen_vec_setv4hi_internal (target, x, index, target));
>           break;
>         case E_V8HImode:
> -         emit_insn (gen_neon_vset_lanev8hi (target, x, target, index));
> +         emit_insn (gen_vec_setv8hi_internal (target, x, index, target));
>           break;
>         case E_V2SImode:
> -         emit_insn (gen_neon_vset_lanev2si (target, x, target, index));
> +         emit_insn (gen_vec_setv2si_internal (target, x, index, target));
>           break;
>         case E_V4SImode:
> -         emit_insn (gen_neon_vset_lanev4si (target, x, target, index));
> +         emit_insn (gen_vec_setv4si_internal (target, x, index, target));
>           break;
>         case E_V2SFmode:
> -         emit_insn (gen_neon_vset_lanev2sf (target, x, target, index));
> +         emit_insn (gen_vec_setv2sf_internal (target, x, index, target));
>           break;
>         case E_V4SFmode:
> -         emit_insn (gen_neon_vset_lanev4sf (target, x, target, index));
> +         emit_insn (gen_vec_setv4sf_internal (target, x, index, target));
>           break;
>         case E_V2DImode:
> -         emit_insn (gen_neon_vset_lanev2di (target, x, target, index));
> +         emit_insn (gen_vec_setv2di_internal (target, x, index, target));
>           break;
>         default:
>           gcc_unreachable ();
>
>
> Can we take the opportunity here to remove that switch statement and use the parametrised names machinery:
> https://gcc.gnu.org/onlinedocs/gccint/Parameterized-Names.html#Parameterized-Names
>
> so that we can instead have one call to gen_vec_setv8hi_internal (mode, target, x, merge_mask, target) or something.

Yes, that's what Richard posted in bugzilla, it's much nicer indeed.

> Thanks,
> Kyrill
>

      reply	other threads:[~2019-07-08  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  9:04 Christophe Lyon
2019-07-08  9:06 ` Richard Sandiford
2019-07-08  9:10   ` Christophe Lyon
2019-07-10 10:20     ` Richard Sandiford
2019-07-10 11:25       ` Ramana Radhakrishnan
2019-07-08  9:09 ` Kyrill Tkachov
2019-07-08  9:16   ` 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=CAKdteOaW8nuGAB4EM3e5MZXJuC5thzfAUdDeZmHWrRO+v++tbA@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    --cc=rguenther@suse.de \
    /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).