From: Florian Weimer <fweimer@redhat.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org, vinschen@redhat.com
Subject: Re: values of FE_TONEAREST...
Date: Thu, 24 Jun 2021 09:36:55 +0200 [thread overview]
Message-ID: <87sg17n27c.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mw35t7raki.fsf@tomate.loria.fr> (Paul Zimmermann's message of "Thu, 24 Jun 2021 09:22:37 +0200")
* Paul Zimmermann:
> I'd like to have the opinion of GNU libc developers on this, especially those
> who are also involved in Redhat Newlib:
>
> https://mailman.oakapple.net/pipermail/cfp-interest/2021-June/002038.html
>
> This was discussed in the last CFP meeting yesterday:
>
> https://mailman.oakapple.net/pipermail/cfp-interest/2021-June/002048.html
I think none of the libraries involved would want to go through the
hassle of an ABI transition. The values have been like this for a long
time.
There are of course other sources of binary incompatibility, such as
different type sizes.
Thanks,
Florian
next prev parent reply other threads:[~2021-06-24 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 7:22 Paul Zimmermann
2021-06-24 7:36 ` Florian Weimer [this message]
2021-06-24 18:19 ` Joseph Myers
2021-06-24 18:02 ` Joseph Myers
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=87sg17n27c.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=Paul.Zimmermann@inria.fr \
--cc=libc-alpha@sourceware.org \
--cc=vinschen@redhat.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).