From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
Alan Lawrence <alan.lawrence@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH 10/11][RS6000] Migrate reduction optabs to reduc_..._scal
Date: Wed, 12 Nov 2014 09:26:00 -0000 [thread overview]
Message-ID: <20141112092635.GA20654@gate.crashing.org> (raw)
In-Reply-To: <20141112012722.GA5485@ibm-tiger.the-meissners.org>
On Tue, Nov 11, 2014 at 08:27:22PM -0500, Michael Meissner wrote:
> > Before the patch, the final reduction used *vsx_reduc_splus_v2df; after
> > the patch, it is *vsx_reduc_plus_v2df_scalar. The former does a vector
> > add, the latter a float add. And it uses the same pseudoregister for the
> > accumulator throughout. IRA decides a register is more expensive than
> > memory for this, I suppose because it wants both V2DF and DF? It doesn't
> > seem to like the subreg very much.
>
> I haven't looked into in detail (I've been a little busy with th upper regs
> patch), but I suspect the problem is that 128-bit and 64-bit types cannot
> overlap (i.e. rs6000_cannot_change_mode_class returns true). This is due to
> the fact that scalars in VSX registers occupy the upper 64-bits, which would
> not match the compiler's notion of that it should be in the bottom 64-bits.
You suspect correctly. Hacking around that in cannot_change_mode_class
doesn't help, subreg_get_info disallows it next.
Changing the pattern so it does two extracts instead of an extract and
a subreg works (you get an fmr for the high part though, register alloc
doesn't know dest=src is for free here).
_Should_ the subreg thing work? Or should the patterns be fixed?
Segher
next prev parent reply other threads:[~2014-11-12 9:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:57 [PATCH v2 0-6/11] Fix PR/61114, make direct vector reductions endianness-neutral Alan Lawrence
2014-10-24 11:58 ` [PATCH 7/11][ARM] Migrate to new reduc_plus_scal_optab Alan Lawrence
2014-11-03 17:32 ` Ramana Radhakrishnan
2014-10-24 12:01 ` [PATCH v2 0-6/11] Fix PR/61114, make direct vector reductions endianness-neutral Richard Biener
2014-10-24 12:05 ` [PATCH 8/11][ARM] Migrate to new reduc_[us](min|max)_scal_optab Alan Lawrence
2014-11-04 11:08 ` Ramana Radhakrishnan
2014-10-24 12:06 ` [PATCH 9/11][i386] Migrate reduction optabs to reduc_..._scal Alan Lawrence
2014-10-24 12:07 ` [PATCH 10/11][RS6000] " Alan Lawrence
2014-10-24 12:14 ` Alan Lawrence
2014-10-25 0:08 ` David Edelsohn
2014-11-03 17:51 ` Bill Schmidt
2014-11-06 16:44 ` Alan Lawrence
2014-11-06 18:57 ` Bill Schmidt
2014-11-07 10:09 ` Alan Lawrence
2014-11-10 22:39 ` Michael Meissner
2014-11-11 7:10 ` Segher Boessenkool
2014-11-12 1:54 ` Michael Meissner
2014-11-12 9:26 ` Segher Boessenkool [this message]
2014-11-12 19:20 ` Michael Meissner
2014-11-12 12:32 ` Alan Lawrence
2014-11-12 18:53 ` Alan Lawrence
2014-12-11 15:59 ` Ping: " Alan Lawrence
2014-12-11 18:37 ` Alan Lawrence
2014-10-24 12:12 ` [Protopatch 11/11][IA64] Migrate to reduc_(plus|min|max)_scal_v2df optab Alan Lawrence
2014-10-24 12:50 ` Alan Lawrence
2014-10-24 15:19 ` [PATCH v2 0-6/11] Fix PR/61114, make direct vector reductions endianness-neutral Matthew Fortune
2014-10-27 11:48 ` Richard Biener
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=20141112092635.GA20654@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=alan.lawrence@arm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@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).