From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Cc: Florian Weimer <fw@deneb.enyo.de>,
Carlos O'Donell <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Bill Schmidt <wschmidt@us.ibm.com>
Subject: Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.
Date: Tue, 26 Jun 2018 20:52:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806262040190.29676@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87a7rh9vw1.fsf@linux.ibm.com>
On Tue, 26 Jun 2018, Tulio Magno Quites Machado Filho wrote:
> Florian Weimer <fw@deneb.enyo.de> writes:
>
> > * Carlos O'Donell:
> >
> >> I'm willing to extend the ABI/API freeze to July 13th for the ppc64le
> >> float128 changes, to allow those to go into the glibc 2.28 release.
> >
> > Do you expect these changes to be specific to the ppc64le ABI, or
> > might there be impact on other ABIs?
>
> They're all specific to the ppc64le ABI.
Handling float128 for argp.h, err.h and error.h functions, while keeping
using the same machinery for header redirections for both float128 long
double and -mlong-double-64 and keeping the machinery as consistent as
possible between different headers, means that all ldbl-opt platforms will
get new symbols __nldbl_argp_error, __nldbl_argp_failure, __nldbl_warn,
__nldbl_vwarn, __nldbl_warnx, __nldbl_vwarnx, __nldbl_err, __nldbl_verr,
__nldbl_errx, __nldbl_verrx, __nldbl_error, __nldbl_error_at_line.
(These are the functions I know about that were missed when the ldbl-opt
machinery was originally set up, but I don't guarantee that list is
complete.) Thus, as well as powerpc64le, all other powerpc systems are
affected, as are alpha, s390 and 32-bit sparc.
(See what I said in
<https://sourceware.org/ml/libc-alpha/2018-05/msg00803.html> regarding the
general strategy of sharing bits/*ldbl.h headers between the different
cases of long double redirections, with new macro variants being added if
necessary to handle cases that need to be distinguished for float128 long
double but not for the present -mlong-double-64 redirections.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-26 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 19:32 Carlos O'Donell
2018-06-26 19:35 ` Florian Weimer
2018-06-26 19:43 ` Tulio Magno Quites Machado Filho
2018-06-26 20:52 ` Joseph Myers [this message]
2018-06-27 2:00 ` Tulio Magno Quites Machado Filho
2018-06-29 14:33 ` Szabolcs Nagy
2018-06-29 14:36 ` Florian Weimer
2018-06-29 15:37 ` Szabolcs Nagy
2018-07-02 13:59 ` Maciej W. Rozycki
2018-07-02 15:22 ` Joseph Myers
2018-07-02 15:40 ` Maciej W. Rozycki
2018-07-03 13:53 ` Carlos O'Donell
2018-07-04 19:35 ` Tulio Magno Quites Machado Filho
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.1806262040190.29676@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.vnet.ibm.com \
--cc=wschmidt@us.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).