I've reassigned this bug from the kernel to gcc-4.0 as we feel that the
solution chosen in the kernel packaging is not really a fix, but a
workaround.
As tests have shown that the problem does not exist when the same kernel
is compiled with gcc-3.3, the real bug is likely in gcc-4.0.
I've "found" the bug for 4.0.1-3 after looking at the dates for relevant
uploads, but as uploads were quite frequent, I could be off by a version
either way.
I've reassigned this bug from the kernel to gcc-4.0 as we feel that the
solution chosen in the kernel packaging is not really a fix, but a
workaround.
As tests have shown that the problem does not exist when the same kernel
is compiled with gcc-3.3, the real bug is likely in gcc-4.0.
I've "found" the bug for 4.0.1-3 after looking at the dates for relevant
uploads, but as uploads were quite frequent, I could be off by a version
either way.
Please see the bug history for details.
Cheers,
FJP