[Bug rtl-optimization/323] optimized code gives strange floating point results

--- Comment #132 from ich at az2000 dot de 2009-07-22 20:54 --- So that means that this C++ example could crash under certain circumstances (depending on how far the compiler is optimising here)? #include #define third ((double)atoi("1")/atoi("3")) int

[Bug rtl-optimization/323] optimized code gives strange floating point results

--- Comment #129 from ich at az2000 dot de 2009-05-18 14:24 --- I am a bit wondering if this bug is also for the case (a < b) && (b < a) == true. Is it? Because if so, this becomes way more serious, as for example std::set is broken then (and depending on the STL impl