Why not push and pop ax a ton?
http://www.os2museum.com/wp/this-code-smells-of-desperation/
PDF for William Kahan's Beastly Numbers paper:
https://people.eecs.berkeley.edu/~wkahan/tests/numbeast.pdf
"It seems unlikely that two computers, designed by different people 1800 miles apart, would be upset in the same way by the same two floating-point numbers 65535... and 4294967295... , but it has happened."
#postmortem #floatingpoint #x87 #cyrix
@esoterica@mathstodon.xyz
#postmortem #floatingpoint #x87 #cyrix
I updated a #haskell package:
https://hackage.haskell.org/package/long-double
An #FFI #binding to #C's #LongDouble #FloatingPoint #number #type. Traditionally on #x86 and #x86_64, long double has been an 80-bit #x87 type, and 32bit #ARM simply aliases to #double, but it seems #gcc on #aarch64 implements long double as #_Float128 which is #IEEE #quadruple #precision; so far tested only with #ghc and #gcc on #aarch64 (the functionality on other architectures should be unaffected).
#ghc #precision #quadruple #ieee #_Float128 #aarch64 #gcc #double #arm #x87 #x86_64 #x86 #type #number #floatingpoint #LongDouble #c #binding #ffi #haskell