On Wed, 11 Jun 2008 08:50:47 +0200 Luca Barbato <[EMAIL PROTECTED]> wrote: > > And saving your ass when you're using a broken compiler that > > generates broken code that would force you to reinstall a working > > compiler by hand when the package manager gets h0rked. > > You (upstream) are supposed to test and early users are supposed to > check their bleeding edge stuff is working if they care enough. > People using released programs that are in stable shouldn't have to > do that.
If everyone running stable used the same base system, tool chain and configuration you would be right. But every Gentoo system is different, so there's no common target to test on. And it's fairly well established that lots stable Gentoo users have broken toolchains... > If your code doesn't survive a gcc release usually it's the code > being wrong most of the times. If you have bad code, yes. If you have good code, instead it's usually gcc's fault. Things like gcc bug 31899 are common enough to be a nuisance. -- Ciaran McCreesh
signature.asc
Description: PGP signature
