Am Sat, 21 Jun 2008 19:03:38 +0200 schrieb Andreas Radke <a.radke@arcor.de>:
Am Fri, 20 Jun 2008 08:09:35 -0500 schrieb "Dan McGee" <dpmcgee@gmail.com>:
This is going to get us when we rebuild a kernel with gcc 4.3.1, so we should probably be aware:
http://kerneltrap.org/Linux/Compiler_Oops https://bugzilla.redhat.com/show_bug.cgi?id=451068
Looks like 2.6.25.6 is built with gcc 4.3.0 so we are safe now. Should we patch gcc with the upstream fix?
-Dan
I'll have a look at it at the beginning of next week. Patching gcc or or changing to their latest stable tree snapshot should also be an option.
-Andy
gcc-{,libs-}4.3.1-2 based on the latest snapshot has hit testing and with all the latest upstream commits included it _should_ fix the regression. so kernel packagers give it a try before we start gcc signoff. -Andy