This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Minimum floating-point requirements
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Steve Munroe <sjmunroe at us dot ibm dot com>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, libc-alpha at sourceware dot org
- Date: Sat, 8 Feb 2014 20:15:17 -0500
- Subject: Re: Minimum floating-point requirements
- Authentication-results: sourceware.org; auth=none
- References: <CAGWvnym4yN=7rLrm0RRtNN++T=xwx8r3MUKJOfz4r+H=Z9zd7Q at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401300038120 dot 24633 at digraph dot polyomino dot org dot uk> <OF9FA4A0A3 dot 0CD33B43-ON86257C70 dot 0073531F-86257C70 dot 0073A4BB at us dot ibm dot com> <Pine dot LNX dot 4 dot 64 dot 1401302108080 dot 12540 at digraph dot polyomino dot org dot uk> <Pine dot LNX dot 4 dot 64 dot 1402072347200 dot 12232 at digraph dot polyomino dot org dot uk>
On Fri, Feb 7, 2014 at 6:51 PM, Joseph S. Myers <joseph@codesourcery.com> wrote:
> Steve, I don't think I've seen any followup to this message
> <https://sourceware.org/ml/libc-alpha/2014-01/msg00714.html>. As I note
> there, I'd be happy with Mike Stump's suggestion of a -mieee option (with
> whatever name the powerpc GCC maintainers might prefer) enabling use of
> new libgcc functions __gcc_qadd_ieee, __gcc_qsub_ieee, __gcc_qmul_ieee,
> __gcc_qdiv_ieee, where would have more careful treatment of exceptions
> (and in future of rounding modes) than the main _gcc_* functions.
Which mode are you and Mike proposing as the default? Based on the
proposed naming, I assume that the current behavior will remain with
the current names of the functions. I assume that -mieee (or whatever
command line option is chosen) will not be the default?
How do you propose this interact with, for example, libstdc++? A
multilib will be odious, but one will not obtain full conformance if
one mixes code that references both sets of symbols.
Or do you propose using the same symbol name and somehow overriding
the default, non-conformant symbols with another library?
Thanks, David