public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 03/10] Rename __LONG_DOUBLE_USES_FLOAT128 to
Date: Fri, 03 Apr 2020 16:22:36 -0300	[thread overview]
Message-ID: <87d08oml1f.fsf@linux.ibm.com> (raw)
In-Reply-To: <20200327211801.31234-4-murphyp@linux.vnet.ibm.com>

"Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org> writes:

> __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI per feedback and disucssion

It seems the subject of the commit and the initial explanation got mixed up.

> diff --git a/bits/long-double.h b/bits/long-double.h
> index 6e16447e65..bdde78f49a 100644
> --- a/bits/long-double.h
> +++ b/bits/long-double.h
> @@ -37,4 +37,17 @@
>  #ifndef __NO_LONG_DOUBLE_MATH
>  # define __NO_LONG_DOUBLE_MATH	1
>  #endif
> -#define __LONG_DOUBLE_USES_FLOAT128 0
> +
> +/* The macro __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI is used to determine the
> +   choice of the underlying ABI of long double.  It will always assume
> +   a constant value for each translation unit.
> +
> +   If the value is non-zero, any API which is parameterized by the long
> +   double type (i.e the scanf/printf family of functions or the explicitly
> +   parameterized math.h functions) will be redirected to a compatible
> +   implementation using _Float128 ABI via symbols suffixed with ieee128.
> +
> +   The mechanism this macro uses to acquire may be a function
> +   of architecture, or target specific options used to invoke the
> +   compiler.  */
> +#define __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI 0

OK.

> diff --git a/sysdeps/ieee754/ldbl-128ibm-compat/bits/long-double.h b/sysdeps/ieee754/ldbl-128ibm-compat/bits/long-double.h
> index 91dddbdc8b..ef834c7748 100644
> --- a/sysdeps/ieee754/ldbl-128ibm-compat/bits/long-double.h
> +++ b/sysdeps/ieee754/ldbl-128ibm-compat/bits/long-double.h
> @@ -22,8 +22,5 @@
>  #  define __NO_LONG_DOUBLE_MATH		1
>  # endif
>  #endif
> -/* On platforms that reuse the _Float128 implementation for IEEE long
> -   double, access to the correct long double functions is selected based
> -   on the long double mode being used during the compilation.  On
> -   powerpc64le, this is true when -mabi=ieeelongdouble is in use.  */
> -#define __LONG_DOUBLE_USES_FLOAT128 (__LDBL_MANT_DIG__ == 113)
> +
> +#define __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI (__LDBL_MANT_DIG__ == 113)

OK.

LGTM with a fixed subject

Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>

-- 
Tulio Magno


  reply	other threads:[~2020-04-03 19:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 21:17 [PATCH v2 00/10] IEEE binary128 long double on powerpc64le Paul E. Murphy
2020-03-27 21:17 ` [PATCH v2 01/10] ldbl-128ibm-compat: workaround C++ redirect limitations Paul E. Murphy
2020-03-27 21:34   ` Joseph Myers
2020-04-01 20:29     ` Paul E Murphy
2020-04-01 20:41       ` DJ Delorie
2020-04-01 23:07       ` Joseph Myers
2020-04-02 16:48         ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 02/10] ldbl-128ibm: simplify iscanonical.h Paul E. Murphy
2020-04-03 20:12   ` Tulio Magno Quites Machado Filho
2020-04-06 16:46     ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 03/10] Rename __LONG_DOUBLE_USES_FLOAT128 to Paul E. Murphy
2020-04-03 19:22   ` Tulio Magno Quites Machado Filho [this message]
2020-03-27 21:17 ` [PATCH v2 04/10] powerpc64le: Enforce -mabi=ibmlongdouble when -mfloat128 used Paul E. Murphy
2020-04-03 19:29   ` Tulio Magno Quites Machado Filho
2020-04-06 16:49     ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 05/10] powerpc64le: workaround ieee long double / _Float128 stdc++ bug Paul E. Murphy
2020-04-03 19:03   ` Tulio Magno Quites Machado Filho
2020-03-27 21:17 ` [PATCH v2 06/10] powerpc64le: raise GCC requirement to 7.3 for long double transition Paul E. Murphy
2020-03-31 20:47   ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 07/10] powerpc64le: bump binutils version requirement to >= 2.26 Paul E. Murphy
2020-04-03 19:36   ` Tulio Magno Quites Machado Filho
2020-03-27 21:17 ` [PATCH v2 08/10] powerpc64le: enforce non-specific long double in .gnu.attributes section Paul E. Murphy
2020-04-03 19:49   ` Tulio Magno Quites Machado Filho
2020-03-27 21:18 ` [PATCH v2 09/10] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0) Paul E. Murphy
2020-04-03 20:38   ` Adhemerval Zanella
2020-04-07 19:57     ` Paul E Murphy
2020-03-27 21:18 ` [PATCH v2 10/10] powerpc64le: Enable support for IEEE long double 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=87d08oml1f.fsf@linux.ibm.com \
    --to=tuliom@ascii.art.br \
    --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).