Displaying 4 results from an estimated 4 matches for "no_honor_infinities".
2020 Jan 27
11
Floating point semantic modes
...ct, may_trap }
fenv_access { on, off }
rounding_mode { dynamic, tonearest, downward, upward, towardzero }
contract { on, off, fast }
denormal_fp_math { IEEE, PreserveSign, PositiveZero }
denormal_fp32_math { IEEE, PreserveSign, PositiveZero }
support_math_errno { on, off }
no_honor_nans { on, off }
no_honor_infinities { on, off }
no_signed_zeros { on, off }
allow_reciprocal { on, off }
allow_approximate_fns { on, off }
allow_reassociation { on, off }
---------------------
Dependencies
---------------------
rounding_mode must be "tonearest" if fenv_access is "off" -- It is the user's resp...
2020 Jan 29
2
Floating point semantic modes
...ct, may_trap }
fenv_access { on, off }
rounding_mode { dynamic, tonearest, downward, upward, towardzero }
contract { on, off, fast }
denormal_fp_math { IEEE, PreserveSign, PositiveZero }
denormal_fp32_math { IEEE, PreserveSign, PositiveZero }
support_math_errno { on, off }
no_honor_nans { on, off }
no_honor_infinities { on, off }
no_signed_zeros { on, off }
allow_reciprocal { on, off }
allow_approximate_fns { on, off }
allow_reassociation { on, off }
---------------------
Dependencies
---------------------
rounding_mode must be "tonearest" if fenv_access is "off" -- It is the user's resp...
2020 Jan 28
3
Floating point semantic modes
...t; semantics depending on how libm is implemented (e.g. glibc will set errno
> independently of how you compiled your code).
>
> > no_honor_nans { on, off }
>
> ideally there would be a way to support snan too.
> (e.g. isnan(x) cannot be turned into x!=x then)
>
> > no_honor_infinities { on, off }
> > no_signed_zeros { on, off }
> > allow_reciprocal { on, off }
> > allow_approximate_fns { on, off }
> > allow_reassociation { on, off }
>
> excess precision handling is missing from this list which matters for x87 and
> m68k fpu support and may matte...
2020 Jan 29
3
Floating point semantic modes
...o checks or calls that set errno can break semantics depending on how libm is implemented (e.g. glibc will set errno independently of how you compiled your code).
> no_honor_nans { on, off }
ideally there would be a way to support snan too.
(e.g. isnan(x) cannot be turned into x!=x then)
> no_honor_infinities { on, off }
> no_signed_zeros { on, off }
> allow_reciprocal { on, off }
> allow_approximate_fns { on, off }
> allow_reassociation { on, off }
excess precision handling is missing from this list which matters for x87 and m68k fpu support and may matter for _Float16 implementations that...