On Thu, 12 Jul 2007, Andi Kleen wrote:
>
> I just checked with today's gcc 4.2 (070711) freshly compiled and from a
> quick inspection
> the code looks correct again. So perhaps it has been already fixed?
Did you see the breakage with the original compiler? It might be some
config setup or something.
But yeah, if Debian/sid is just using random compiler snapshots of the
day, I htink we can just bury this as "pointless".
Who the heck takes a compiler snapshot and runs with it? At least when
your kernel breaks, it seldom breaks subtly (but I would expect that most
distros would not pick random nightly kernel builds). When your compiler
breaks, you have random problems in totally unexpected places, the last
thing you want to have is a random nightly snapshot in a distro - even a
development one.
Strange.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
