| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 26 Oct 2010 11:19:00 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Andi Kleen <andi@...stfloor.org> CC: kvm@...r.kernel.org, avi@...hat.com, linux-kernel@...r.kernel.org Subject: Re: fyi: gcc33-hammer crashes when compiling kvm emulate.c On 10/26/2010 10:01 AM, Andi Kleen wrote: >> Not unless they are actively known to break. People get huffy about it > > Well they do -- i just found out. Sounds like a good reason to put in a warning or error. >> because even if it is known to have problems it doesn't break *their* >> particular configuration. I'm getting to be of the opinion that people >> who compile modern kernels with ancient compilers and expect it to work >> are suffering from some particular kind of insanity -- it's nothing the >> distros do. The only exception are embedded people who compile with the >> latest 3.4 gcc; they have explained they do so because newer gccs have >> too many dependencies (the actual compiler, not the generated code) and >> for speed. > > At least in the old days the main reason for gcc 3 was build speed. > AKPM and some others used to be fond of that. > > 3.x is apparently much faster than 4.x That is an issue too, as 3.x does a lot fewer optimizations than 4.x. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists