Open eliaslfox opened 1 year ago
Same bug on Linux x86-64.
We end up calling zerop on the NaN value as part of turning the typespec into a ctype.
To be honest, I am not sure what to do here.
Probably use ccl::nan-or-infinity-p
to prevent zerop
been called on nan.
However, zerop
seems should not raise invalid operation exception on NaN at all, for the reason that compare quiet NaN with zero should just give false without signaling, but I'm not able to understand the assembly code to find out why the exception is raised for =
with two double floats.
On macOS using
CCL Version 1.12.1 DarwinX8664