This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "Maciej W. Rozycki" <macro at imgtec dot com>
- Cc: <linux-mips at linux-mips dot org>, <libc-alpha at sourceware dot org>, <binutils at sourceware dot org>, <gcc at gcc dot gnu dot org>, Matthew Fortune <Matthew dot Fortune at imgtec dot com>, Daniel Sanders <Daniel dot Sanders at imgtec dot com>, Leonid Yegoshin <Leonid dot Yegoshin at imgtec dot com>
- Date: Tue, 17 Nov 2015 15:07:40 +0000
- Subject: Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 00 dot 1511140411050 dot 7097 at tp dot orcam dot me dot uk>
On Sat, 14 Nov 2015, Maciej W. Rozycki wrote:
> Any or all of these options may have effects beyond propagating the IEEE
> Std 754 compliance mode down to the assembler and the linker. In
> particular `-mieee=strict' is expected to guarantee code generated to
> fully comply to IEEE Std 754 rather than only as far as NaN representation
> is concerned.
"guarantee" seems rather strong given the various known issues with (lack
of) Annex F support in GCC. Do you have any actual configuration in mind
it would affect, MIPS-specific or otherwise? For
non-architecture-specific things, -std= options for C standards
conformance are meant to enable whatever options are required (e.g. they
disable the default -ffp-contract=fast), without affecting things not
required by the standards by default (so they don't enable -frounding-math
or -fsignaling-nans, for example).
--
Joseph S. Myers
joseph@codesourcery.com