Can this bug be reproduced with upstream gcc-4_0-branch as of date 20051023,
which is what Debian's gcc-4.0 4.0.2-3 is based on?
If so, it should be reported upstream; upstream has several people who often
run automated binary regression searches and should be able to identify the
commit which caused this.
Can this bug be reproduced with upstream gcc-4_0-branch as of date 20051023,
which is what Debian's gcc-4.0 4.0.2-3 is based on?
If so, it should be reported upstream; upstream has several people who often
run automated binary regression searches and should be able to identify the
commit which caused this.
--
Nathanael Nerode <email address hidden>
"(Instead, we front-load the flamewars and grudges in lists.debian. org/debian- devel/2005/ 09/msg01056. html
the interest of efficiency.)" --Steve Lanagasek,
http://