From: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCHv3 1/4] ldbl-128: Rename 'long double' to '_Float128'
Date: Wed, 31 Aug 2016 18:27:00 -0000 [thread overview]
Message-ID: <b8bcfc8d-afaf-0f83-233c-3d2f068ae5b4@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608311701390.6827@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On 08/31/2016 12:02 PM, Joseph Myers wrote:
> 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).
Attached is a patch to cleanup e_gammal_r.c. I didn't come
across any others. OK too?
[-- Attachment #2: 0001-ldbl-128-Cleanup-e_gammal_r.c-after-_Float128-rename.patch --]
[-- Type: text/x-patch, Size: 1696 bytes --]
From 25113f286be4ac32a124404b178f244c9508c954 Mon Sep 17 00:00:00 2001
From: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
Date: Wed, 31 Aug 2016 13:17:35 -0500
Subject: [PATCH] ldbl-128: Cleanup e_gammal_r.c after _Float128 rename
* sysdeps/ieee754/ldbl-128/e_gammal_r.c:
(gammal_positive): Fix spacing.
(__ieee754_gammal_r): Likewise.
---
sysdeps/ieee754/ldbl-128/e_gammal_r.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/sysdeps/ieee754/ldbl-128/e_gammal_r.c b/sysdeps/ieee754/ldbl-128/e_gammal_r.c
index 43282fe..ac68b31 100644
--- a/sysdeps/ieee754/ldbl-128/e_gammal_r.c
+++ b/sysdeps/ieee754/ldbl-128/e_gammal_r.c
@@ -105,10 +105,10 @@ gammal_positive (_Float128 x, int *exp2_adj)
}
*exp2_adj = x_adj_log2 * (int) x_adj_int;
_Float128 ret = (__ieee754_powl (x_adj_mant, x_adj)
- * __ieee754_exp2l (x_adj_log2 * x_adj_frac)
- * __ieee754_expl (-x_adj)
- * __ieee754_sqrtl (2 * M_PIl / x_adj)
- / prod);
+ * __ieee754_exp2l (x_adj_log2 * x_adj_frac)
+ * __ieee754_expl (-x_adj)
+ * __ieee754_sqrtl (2 * M_PIl / x_adj)
+ / prod);
exp_adj += x_eps * __ieee754_logl (x_adj);
_Float128 bsum = gamma_coeff[NCOEFF - 1];
_Float128 x_adj2 = x_adj * x_adj;
@@ -188,8 +188,8 @@ __ieee754_gammal_r (_Float128 x, int *signgamp)
if (frac > 0.5L)
frac = 1.0L - frac;
_Float128 sinpix = (frac <= 0.25L
- ? __sinl (M_PIl * frac)
- : __cosl (M_PIl * (0.5L - frac)));
+ ? __sinl (M_PIl * frac)
+ : __cosl (M_PIl * (0.5L - frac)));
int exp2_adj;
ret = M_PIl / (-x * sinpix
* gammal_positive (-x, &exp2_adj));
--
2.4.11
next prev parent reply other threads:[~2016-08-31 18:27 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 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
2016-08-31 18:27 ` Paul E. Murphy [this message]
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:29 ` [PATCHv3 4/4] ldbl-128: Manually cleanup whitespace issues from L(x) application 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
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
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=b8bcfc8d-afaf-0f83-233c-3d2f068ae5b4@linux.vnet.ibm.com \
--to=murphyp@linux.vnet.ibm.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).