You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Brad has pointed out, it is an error to pass 0 as a second argument to ##fx*?. The reason is that it uses division to check if the multiplication overflowed. That is (##fx*? a b) computes r = a*b (modulo the word size), and then checks if r/b=a (if it does there was no overflow).
gsi trace:
> (##fx* 0 1)
0
> (##fx* 1 0)
0
> (##fx*? 0 1)
0
> (##fx*? 1 0)
Floating point exception
The same behavior appears each time the right operand is 0.
The text was updated successfully, but these errors were encountered: