[RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking
Joseph Myers
joseph@codesourcery.com
Tue Nov 17 15:07:00 GMT 2015
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
More information about the Binutils
mailing list