----- Original Message ----- From: "Ruben Van Boxem" > I feel compelled to say that if you are subtracting floats to check for > equality, you should be smacked in the face.
No, I'm not doing that :-) But I should have provided a brief description of what it *is* demonstrating. It demonstrates that convert(divide1(a, b)) and divide2(a, b) yield different results even though they do the same thing. (Of course, under the hood, they're doing different things - unless the -ffloat-store option is supplied, whereupon the 2 methods *do* provide identical results) Note that convert(), divide1() and divide2() are 3 simple functions defined in demo.c (which was attached to my original post). But with the 64-bit compiler, convert(divide1(a, b)) and divide2(a, b) *always* produce *identical* results. I'm wondering what accounts for this difference between the 32-bit and 64-bit compilers (answer provided in this thread by Lajos), and if/how I can force the 64-bit compiler to produce the same anomaly that the 32-bit compiler can produce. I have no practical need that calls for the 64-bit compiler to produce the anomaly ... I'm just curious to know if it can be done. Cheers, Rob ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
