From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Michael Meissner <meissner@linux.vnet.ibm.com>,
Guozhi Wei <carrot@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH], rs6000 cleanup, make constraints tighter
Date: Mon, 11 Aug 2014 17:21:00 -0000 [thread overview]
Message-ID: <20140811172141.GA29315@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <CAGWvny=FhfHB+nFe-tf1RRLQwr6FEF5RB_m-H9_+CH1_EbK2AA@mail.gmail.com>
On Fri, Aug 08, 2014 at 03:31:48PM -0400, David Edelsohn wrote:
> Okay.
>
> Note that you or Carrot will have to be careful about the merge of
> movdi_internal64 as both of your patches affect that pattern.
Carrot has checked in his patch, and I will adapt my patch (and replace the
constraint wm Carrot used with wi, since wi is now the constraint to use for
DImode in FP/VSX registers.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.vnet.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2014-08-11 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 18:42 Michael Meissner
2014-08-08 19:31 ` David Edelsohn
2014-08-11 17:21 ` Michael Meissner [this message]
2014-08-11 19:52 ` Michael Meissner
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=20140811172141.GA29315@ibm-tiger.the-meissners.org \
--to=meissner@linux.vnet.ibm.com \
--cc=carrot@google.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).