>So? Does that mean the bug doesn't affect GCC 4.1? In that case, I >believe Peter is correct that the bug must be resolved before GCC 4.2 >can enter unstable. Do you agree? That wasn't text i wrote it was text i was quoting. I was just asking if anyone knew if there was a bug report on the issue that hasn't been rejected by those it was reported to. A quick check doesn't seem to find anything in the gcc or debian bugtrackers.