public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 6/6] powerpc64le: Enable support for IEEE long double
Date: Wed, 22 Apr 2020 17:15:04 +0200	[thread overview]
Message-ID: <87v9lrimbr.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <cb74a63078fbbcd09a5c4eb6dd7d3ddc89234f0d.1586199342.git.murphyp@linux.vnet.ibm.com> (Paul E. Murphy via Libc-alpha's message of "Mon, 6 Apr 2020 14:12:39 -0500")

* Paul E. Murphy via Libc-alpha:

> diff --git a/NEWS b/NEWS
> index 07da1545b4..a54c0e0f65 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -14,6 +14,11 @@ Major new features:
>  * The GNU C Library now loads audit modules listed in the DT_AUDIT and
>    DT_DEPAUDIT dynamic section entries of the main executable.
>  
> +* powerpc64le supports IEEE128 long double libm/libc redirects when
> +  using the -mabi=ieeelongdouble to compile C code on supported GCC
> +  toolchains.  It is recommended to use GCC 8 or newer when testing
> +  this option.

Why do you write “testing this option”?

To me, this implies that the feature is not ready yet.  Is that the
case?

  parent reply	other threads:[~2020-04-22 15:15 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
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 [this message]
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=87v9lrimbr.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --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).