http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47763
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-02-16 08:08:33 UTC --- (In reply to comment #4) > Yeah, normally we don't care about such cases. But this one comes from > dhrystone. If it can be fixed cleanly, why not do it? Then the whole dhrystone benchmark is invalid and should not be trusted. I think people should report the bug to the benchmark maker and then declare all previous results of the benchmark as invalid. In fact any benchmark which depends on undefined code should not be trusted.
