------- Comment #8 from uweigand at gcc dot gnu dot org 2010-05-11 13:57 ------- (In reply to comment #7) > Not sure what's the state here. Is 4.4 broken now?
Here's the status as far as I know. I had checked in a patch: http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00254.html to fix the problem PR 37053. This patch introduced the regression described in the current problem, fixed by Hans-Peter's patch above. Now, *both* my PR 37053 patch and Hans-Peter's patch were checked in only to mainline (i.e. GCC 4.5); GCC 4.4 should not be affected either way. However, this means the original problem in PR 37053 is still present in GCC 4.4. And in fact, it may well be the case that the problem described in PR 40414 is actually a duplicate of PR 37053. In this case, I guess the way to go would be to apply *both* my patch and Hans-Peter's patch to the 4.4 branch ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41064
