From: Richard Biener <richard.guenther@gmail.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/3] testsuite: Require 128-bit vectors for bb-slp-pr95839.c
Date: Thu, 20 Jul 2023 09:15:52 +0200 [thread overview]
Message-ID: <CAFiYyc0Li19JB1pU5jVdPUCXBEMfmPWWdLX31uqR7ecLetnRBA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2307191134510.28892@tpp.orcam.me.uk>
On Wed, Jul 19, 2023 at 4:34 PM Maciej W. Rozycki <macro@embecosm.com> wrote:
>
> On Wed, 12 Jul 2023, Richard Biener wrote:
>
> > > > That said, we should handle this better so can you file an
> > > > enhancement bugreport for this?
> > >
> > > Filed as PR -optimization/110630.
> >
> > Thanks!
>
> Thanks for making this improvement. I've checked MIPS results and code
> produced now is as follows:
>
> daddiu $sp,$sp,-64
> sd $5,24($sp)
> sd $7,40($sp)
> ldc1 $f0,24($sp)
> ldc1 $f1,40($sp)
> sd $4,16($sp)
> sd $6,32($sp)
> ldc1 $f2,32($sp)
> add.ps $f1,$f0,$f1
> ldc1 $f0,16($sp)
> add.ps $f0,$f0,$f2
> sdc1 $f1,56($sp)
> ld $3,56($sp)
> sdc1 $f0,48($sp)
> ld $2,48($sp)
> jr $31
> daddiu $sp,$sp,64
>
> which does do vector stuff now, although it's still considerably worse
> than my handwritten example:
>
> > > dmtc1 $4,$f0
> > > dmtc1 $5,$f1
> > > dmtc1 $6,$f2
> > > dmtc1 $7,$f3
> > > add.ps $f0,$f0,$f1
> > > add.ps $f2,$f2,$f3
> > > dmfc1 $2,$f0
> > > jr $31
> > > dmfc1 $3,$f2
>
> Or I'd say it's pretty terrible, but given the current situation with the
> MIPS backend I'm going to leave it to the new maintainer to sort out.
Yeah, I also wondered what is wrong ... I suspect it's the usual issue
of parameter passing causing spilling ...
> > > Do you agree it still makes sense to include bb-slp-pr95839-v8.c with the
> > > testsuite?
> >
> > Sure, more coverage is always nice.
>
> Thanks, committed (with the `vect64' requirement removed, as we can take
> it for granted with `vect_float').
>
> Maciej
next prev parent reply other threads:[~2023-07-20 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 21:35 [PATCH 0/3] testsuite: Exclude vector tests for unsupported targets Maciej W. Rozycki
2023-07-06 21:35 ` [PATCH 1/3] testsuite: Add check for vectors of 128 bits being supported Maciej W. Rozycki
2023-07-07 6:24 ` Richard Biener
2023-07-11 15:00 ` Maciej W. Rozycki
2023-07-06 21:36 ` [PATCH 2/3] testsuite: Require 128-bit vectors for bb-slp-pr95839.c Maciej W. Rozycki
2023-07-07 6:33 ` Richard Biener
2023-07-11 15:01 ` Maciej W. Rozycki
2023-07-12 7:15 ` Richard Biener
2023-07-19 14:34 ` Maciej W. Rozycki
2023-07-20 7:15 ` Richard Biener [this message]
2023-07-20 9:16 ` Maciej W. Rozycki
2023-07-20 12:09 ` Richard Biener
2023-07-20 13:02 ` Maciej W. Rozycki
2023-07-06 21:36 ` [PATCH 3/3] testsuite: Require vectors of doubles for pr97428.c Maciej W. Rozycki
2023-07-07 6:33 ` Richard Biener
2023-07-11 15:01 ` Maciej W. Rozycki
2023-07-12 7:15 ` Richard Biener
2023-07-19 10:29 ` Maciej W. Rozycki
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=CAFiYyc0Li19JB1pU5jVdPUCXBEMfmPWWdLX31uqR7ecLetnRBA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@embecosm.com \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=yunqiang.su@cipunited.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).