Re:Beating Floating Point at Its Own Game: Posit Arithmetic ...
by dbcurtis on Saturday July 01, 2017 @10:31AM
(#14677241)
Interrupts on NaNs are extremely expensive to implement on vector and GPU processors. We learned that in the Cray-1 days. Handling the exception in a vector iperation kicks off an ultra-expensive context switch. A NaN does not break the flow.
[ Parent
| on HN ]
Re:Beating Floating Point at Its Own Game: Posit Arithmetic ...
by dnautics on Saturday July 01, 2017 @10:54AM
(#14677362)
It seems like an antipattern. If your execution time is bound by an "ultra expensive context switch" occurring when you hit a Nan, then something is wrong with your algorithm.
Re:Beating Floating Point at Its Own Game: Posit Arithmetic ...
by geezerjay on Sunday July 02, 2017 @12:09PM
(#14683088)
> Interrupts on NaNs are extremely expensive to implement on vector and GPU processors.
That's ok, because NaNs are exceptional responses to numerical errors thrown during number crunching, indicating that something failed unexpectedly and the output is crap.