public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul E Murphy <murphyp@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 2/6] Rename __LONG_DOUBLE_USES_FLOAT128 to __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI
Date: Wed, 15 Apr 2020 09:21:21 -0500	[thread overview]
Message-ID: <a5bbec56-e063-d64b-2432-b1fff8071cb3@linux.ibm.com> (raw)
In-Reply-To: <051ed553501de83ffdf59ac09dd2a73c29f69343.1586199342.git.murphyp@linux.vnet.ibm.com>



On 4/6/20 2:12 PM, Paul E. Murphy via Libc-alpha wrote:
> per feedback and disucssion on libc-alpha [2].  Likewise, add
> documentation to the macro in the common bits/long-double.h header.
> This is effectively V2 of [2].
> 
> Per the feedback from Joseph [1].  Good comments and a more
> self-explanatory macro name will be very helpful when this
> macro is able to assume a non-zero value.
> 
> [1] <https://sourceware.org/legacy-ml/libc-alpha/2020-02/msg00687.html>
> [2] <https://sourceware.org/pipermail/libc-alpha/2020-February/111148.html>
> 
> ---8<---
> 
> Improve the commentary to aid future developers who will stumble
> upon this novel, yet not always perfect, mechanism to support
> alternative formats for long double.
> 
> Likewise, rename __LONG_DOUBLE_USES_FLOAT128 to
> __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI now that development work
> has settled down.  The command used was
> 
> git grep -l __LONG_DOUBLE_USES_FLOAT128 ':!./ChangeLog*' | \
>    xargs sed -i 's/__LONG_DOUBLE_USES_FLOAT128/__LDOUBLE_REDIRECTS_TO_FLOAT128_ABI/g'
> ---
>   argp/argp.h                                       |  2 +-
>   bits/long-double.h                                | 15 ++++++++++++++-
>   elf/tst-addr1.c                                   |  2 +-
>   include/math.h                                    |  6 +++---
>   include/monetary.h                                |  2 +-
>   include/printf.h                                  |  2 +-
>   include/stdio.h                                   |  8 ++++----
>   include/stdlib.h                                  |  4 ++--
>   include/sys/cdefs.h                               |  2 +-
>   include/wchar.h                                   |  2 +-
>   libio/bits/stdio-ldbl.h                           |  4 ++--
>   libio/stdio.h                                     |  8 ++++----
>   math/complex.h                                    |  4 ++--
>   math/math.h                                       | 12 ++++++------
>   math/test-ldouble.h                               |  2 +-
>   misc/err.h                                        |  2 +-
>   misc/error.h                                      |  2 +-
>   misc/sys/cdefs.h                                  |  4 ++--
>   misc/sys/syslog.h                                 |  2 +-
>   stdio-common/printf.h                             |  2 +-
>   stdio-common/tst-vfprintf-user-type.c             |  2 +-
>   stdlib/bits/stdlib-ldbl.h                         |  2 +-
>   stdlib/monetary.h                                 |  2 +-
>   stdlib/stdlib.h                                   |  2 +-
>   sysdeps/ieee754/ldbl-128/bits/long-double.h       |  2 +-
>   .../ieee754/ldbl-128ibm-compat/bits/long-double.h |  7 ++-----
>   sysdeps/ieee754/ldbl-128ibm-compat/math_ldbl.h    |  2 +-
>   sysdeps/ieee754/ldbl-128ibm/bits/iscanonical.h    |  2 +-
>   sysdeps/ieee754/ldbl-128ibm/ieee754.h             |  6 +++---
>   .../ldbl-128ibm/include/bits/iscanonical.h        |  2 +-
>   sysdeps/ieee754/ldbl-96/bits/long-double.h        |  2 +-
>   sysdeps/ieee754/ldbl-opt/bits/long-double.h       |  2 +-
>   sysdeps/mips/ieee754/bits/long-double.h           |  2 +-
>   .../sysv/linux/sparc/sparc32/bits/long-double.h   |  2 +-
>   .../sysv/linux/sparc/sparc64/bits/long-double.h   |  2 +-
>   wcsmbs/bits/wchar-ldbl.h                          |  4 ++--
>   wcsmbs/wchar.h                                    |  8 ++++----
>   37 files changed, 74 insertions(+), 64 deletions(-)

Ping?

  reply	other threads:[~2020-04-15 14:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 19:12 [PATCH v3 0/6] IEEE binary128 long double on powerpc64le Paul E. Murphy
2020-04-06 19:12 ` [PATCH v3 1/6] ldbl-128ibm-compat: workaround GCC 9 C++ BZ 90731 Paul E. Murphy
2020-04-15 14:20   ` Paul E Murphy
2020-04-22 14:58     ` Paul E Murphy
2020-04-22 15:11   ` Florian Weimer
2020-04-22 21:17     ` Paul E Murphy
2020-04-23  5:48       ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 2/6] Rename __LONG_DOUBLE_USES_FLOAT128 to __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI Paul E. Murphy
2020-04-15 14:21   ` Paul E Murphy [this message]
2020-04-22 14:59     ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 3/6] powerpc64le: raise GCC requirement to 7.4 for long double transition Paul E. Murphy
2020-04-22 15:19   ` Florian Weimer
2020-04-22 19:33     ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 4/6] powerpc64le: bump binutils version requirement to >= 2.26 Paul E. Murphy
2020-04-22 15:20   ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 5/6] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0) Paul E. Murphy
2020-04-22 15:23   ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 6/6] powerpc64le: Enable support for IEEE long double Paul E. Murphy
2020-04-22 15:03   ` Paul E Murphy
2020-04-22 15:15   ` Florian Weimer
2020-04-22 16:20     ` Paul E Murphy
2020-04-22 16:23       ` Florian Weimer

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=a5bbec56-e063-d64b-2432-b1fff8071cb3@linux.ibm.com \
    --to=murphyp@linux.ibm.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).