On 11 July 2014 03:11, Jeff Epler <[email protected]> wrote: > This means that, in that tiny fraction of cases where you read a mixed > value, you read a value that is accurate in its sign bit, its exponent, > and 21 bits of its mantissa. The rest of the time, of course, you get > the full 53 bits of precision. Contrast that to if we changed hal_float_t > to a float: You get 24 bits of precision, all the time.
I guess an important consideration is that both values were individually valid when written. The worst-case would be a wrap in the lower bits, but it seems unlikely that many processes are even monotonic in that lower 32 bits. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
