------- Additional Comments From nathan at gcc dot gnu dot org 2005-07-01 11:39 ------- (In reply to comment #8) > This fix has not made it to the gcc_4_0 branch, and the problem still exists > in > gcc4.0.0. It is trivially recreated using the same test code:
the bug is not a regression, so it has not gone into 4.0. As there seems to be a need for it, and the patch is small, we could probably do it. Right now 4.0 is frozen for 4.0.1 though -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20746