> disabling/enabling makes this api a lot heavier
> than before, but trapping cannot be decided at
> compile-time, although the result may be cached,
> i think this should not be a frequent operation.
>
> otoh rereading my patch i think i fail to restore
> the original exception state correctly.
On 15/11/16 16:22, FX wrote:
>> There seems to be a separate api for checking trapping support:
>> ieee_support_halting, but it only checked if the exception status
>> flags are available, so check trapping support too by enabling
>> and disabling traps.
>
> Thanks for the patch.
>
> I am worried
Hi,
> There seems to be a separate api for checking trapping support:
> ieee_support_halting, but it only checked if the exception status
> flags are available, so check trapping support too by enabling
> and disabling traps.
Thanks for the patch.
I am worried about the unnecessary operations th
When fpu trapping is enabled in libgfortran, the return value of
feenableexcept is not checked. Glibc reports there if the operation
was unsuccessful which happens if the target has no trapping support.
There seems to be a separate api for checking trapping support:
ieee_support_halting, but it o
