From: Joseph Myers <joseph@codesourcery.com>
To: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCHv3 1/4] ldbl-128: Rename 'long double' to '_Float128'
Date: Wed, 31 Aug 2016 17:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1608311701390.6827@digraph.polyomino.org.uk> (raw)
In-Reply-To: <9870db45-594e-c5df-a0fd-750b4ca11ec8@linux.vnet.ibm.com>
On Wed, 31 Aug 2016, Paul E. Murphy wrote:
> On 08/30/2016 12:16 PM, Joseph Myers wrote:
> > On Tue, 30 Aug 2016, Paul E. Murphy wrote:
> >
> >> Is there any objection to committing patches 1 and
> >> 2 once approved?
> >
> > I don't intend to review patch 2 until patch 1 is in.
> >
>
> For my clarity, is the revised v3 patch 1 OK for commit?
Yes, given a followup to fix indentation in cases where we have
long double var = (expression
continued);
and so changing long double to _Float128 requires the following lines in
the continued expression to be reindented (that appears twice in
e_gammal_r.c, at least).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-08-31 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 16:28 [PATCHv3 0/4] Enable sharing of ldbl-128 with float128 Paul E. Murphy
2016-08-24 16:29 ` [PATCHv3 4/4] ldbl-128: Manually cleanup whitespace issues from L(x) application Paul E. Murphy
2016-08-24 16:29 ` [PATCHv3 1/4] ldbl-128: Rename 'long double' to '_Float128' Paul E. Murphy
2016-08-26 21:55 ` Joseph Myers
2016-08-30 15:31 ` Paul E. Murphy
2016-08-30 17:16 ` Joseph Myers
2016-08-31 15:40 ` Paul E. Murphy
2016-08-31 17:03 ` Joseph Myers [this message]
2016-08-31 18:27 ` Paul E. Murphy
2016-08-31 20:37 ` Joseph Myers
2016-08-31 22:29 ` Paul E. Murphy
2016-08-30 17:42 ` Joseph Myers
2016-08-24 16:30 ` [PATCHv3 3/4] ldbl-128: Mechanical L(x) cleanup Paul E. Murphy
2016-08-26 22:18 ` Joseph Myers
2016-08-29 13:44 ` Paul E. Murphy
2016-08-24 16:30 ` [PATCHv3 2/4] ldbl-128: Use L(x) macro for long double constants Paul E. Murphy
2016-09-02 15:10 ` Joseph Myers
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=alpine.DEB.2.20.1608311701390.6827@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=murphyp@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).