http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47324
--- Comment #54 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-02-13 18:56:48 UTC --- (In reply to comment #53) > I'd rather know two things, that we have a lot of time on the new code and it > works fine znd why the branch doesn't have the problem in similar cases. If > one cannot find a bug to fix, a bug might not exist. If it doesn't exist, > there is nothing to fix. Looking at the x86_64-apple-darwin10 results on gcc-testresults, PR47324 appeared after r162035 and by r162199. I can do a regression hunt through those to see which exact commit triggered them and verify that this hasn't been backported to gcc-4_5-branch.
