From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, rs6000] Prefer vspltisw/h over xxspltib+instruction when available
Date: Wed, 22 Jun 2016 14:22:00 -0000 [thread overview]
Message-ID: <20160622142222.GB5022@gate.crashing.org> (raw)
In-Reply-To: <17065109-773A-402B-9550-2827CAEE4E3C@linux.vnet.ibm.com>
On Tue, Jun 21, 2016 at 06:46:57PM -0500, Bill Schmidt wrote:
> >> When I did this, I ran into a problem with an existing test case. We end up matching the *vsx_splat_v4si_internal pattern instead of falling back to the altivec_vspltisw pattern. The constraints don't match for constant input. To avoid this, I added a pattern ahead of this one that will match for VMX output registers and produce the vspltisw as desired. This corrected the failing test and produces the expected code.
> >
> > Why does the predicate allow constant input, while the constraints do not?
>
> I have no idea why it was built that way. The predicate seems to provide for all sorts of things, but this and the subsequent pattern both handle only a subset of the constraints implied by it. To be honest, I didn't feel competent to try to fix the existing patterns. Do you have any suggestions for what to do instead?
Don't give up so easily? ;-)
The predicate should be tightened, the expander should use a new predicate
that allows all those other things. The hardest part is figuring a good
name for it ;-)
Segher
next prev parent reply other threads:[~2016-06-22 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 20:15 Bill Schmidt
2016-06-21 22:34 ` Segher Boessenkool
2016-06-21 23:47 ` Bill Schmidt
2016-06-22 14:22 ` Segher Boessenkool [this message]
2016-06-22 21:30 ` Michael Meissner
2016-06-22 23:51 ` Segher Boessenkool
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=20160622142222.GB5022@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=wschmidt@linux.vnet.ibm.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).