John Gustafson’s crusade to replace floating point with something better

Re:John Gustafson’s crusade to replace floating point with s... by it_aint_that on Tuesday July 09, 2019 @01:30AM (#20389236)

x87 has been functionally superseded (largely by various SSE iterations), but it is still supported for backwards-compatibility.

Modern applications and compilers largely do not use x87, but they can, and x87 results depending on hidden bits persists in modern x86_64 CPUs.

[ Parent | on HN ]

Re:John Gustafson’s crusade to replace floating point with s... by Zardoz84 on Tuesday July 09, 2019 @04:25AM (#20389881)

DLang allow to use it explicitly by using Real type, I instead of Double and Float types.

[ Parent | on HN ]

Re:John Gustafson’s crusade to replace floating point with s... by enriquto on Tuesday July 09, 2019 @04:00AM (#20389790)

yet it is still used for arithmetic with "long double"

[ Parent | on HN ]

Re:John Gustafson’s crusade to replace floating point with s... by josefx on Wednesday July 10, 2019 @01:58AM (#20399479)

Wouldn't that resovle the issue? long double contains the whole 80 bit state, not much space for undefined bits left.

[ Parent | on HN ]

Re:John Gustafson’s crusade to replace floating point with s... by enriquto on Wednesday July 10, 2019 @04:31AM (#20400165)

Yes, it resolves the issue in practice. However, the issue is an implementation detail of the compiler, not of the floating point format itself.

[ Parent | on HN ]