From: David Edelsohn <dje.gcc@gmail.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
"Maciej W. Rozycki" <macro@codesourcery.com>,
pattyo.lists@gmail.com,
Segher Boessenkool <segher@kernel.crashing.org>,
Olivier Hainque <hainque@adacore.com>,
David Malcolm <dmalcolm@redhat.com>
Subject: Re: PATCH [6 of 7], rs6000, add support for scalar floating point in Altivec registers
Date: Mon, 17 Nov 2014 05:06:00 -0000 [thread overview]
Message-ID: <CAGWvnymscxT83j90PowdiobyKS0Z9+Fy_ooKFF8-6tgFUmtaGg@mail.gmail.com> (raw)
In-Reply-To: <20141112011901.GF3720@ibm-tiger.the-meissners.org>
On Tue, Nov 11, 2014 at 8:19 PM, Michael Meissner
<meissner@linux.vnet.ibm.com> wrote:
> This patch documents the previously undocumented -mupper-regs-df and
> -mupper-regs-sf switches. It also provides feature test macros that users can
> use to determine if the upper register support is enabled.
>
> Once the prevous patches have gone in, is this patch ok to install?
>
> 2014-11-11 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> * config/rs6000/rs6000.opt (-mupper-regs-df): Make option public.
> (-mupper-regs-sf): Likewise.
>
> * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
> __UPPER_REGS_DF__ if -mupper-regs-df. Define __UPPER_REGS_SF__ if
> -mupper-regs-sf.
>
> * doc/invoke.texi (RS/6000 and PowerPC Options): Document
> -mupper-regs-{sf,df}.
Okay.
Thanks, David
next prev parent reply other threads:[~2014-11-17 2:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 0:34 PATCH [intro], " Michael Meissner
2014-11-12 0:58 ` PATCH [patch 1 of 7], " Michael Meissner
2014-11-13 2:28 ` David Edelsohn
2014-11-12 1:05 ` PATCH [2 " Michael Meissner
2014-11-13 2:36 ` David Edelsohn
2014-11-12 1:09 ` PATCH [3 " Michael Meissner
2014-11-13 3:08 ` David Edelsohn
2014-11-12 1:11 ` PATCH [4 " Michael Meissner
2014-11-17 2:56 ` David Edelsohn
2014-11-12 1:21 ` PATCH [6 " Michael Meissner
2014-11-17 5:06 ` David Edelsohn [this message]
2014-11-12 1:21 ` PATCH [5 " Michael Meissner
2014-11-17 2:56 ` David Edelsohn
2014-11-12 1:29 ` PATCH [7 " Michael Meissner
2014-11-17 5:12 ` David Edelsohn
2014-11-14 20:47 ` PATCH [8 of 8], " Michael Meissner
2014-11-17 6:31 ` David Edelsohn
2014-11-20 22:30 ` PATCH, PR 63965, " Michael Meissner
2014-11-21 4:47 ` David Edelsohn
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=CAGWvnymscxT83j90PowdiobyKS0Z9+Fy_ooKFF8-6tgFUmtaGg@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=joseph@codesourcery.com \
--cc=macro@codesourcery.com \
--cc=meissner@linux.vnet.ibm.com \
--cc=pattyo.lists@gmail.com \
--cc=segher@kernel.crashing.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).