http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53916
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |rsandifo at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org>
---
Thanks for the report. As you say, the bug was fixed in the 4.7 timeframe.
The fix was rather invasive and probably wouldn't be safe to backport to 4.6.
I'm therefore going to treat this bug report as being about the poor
quality of the code produced by 4.7. This was actually an unintended
consequence of same the fix.
I've just applied a patch to allow the same division to be used once
again for both results:
http://gcc.gnu.org/ml/gcc-patches/2013-05/msg01568.html
Here too I don't think it's suitable for a backport. The earliest
candidate would be 4.8.2, but it seems too risky for what by then
would be a relatively mature branch.
