| 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
| ||
|
Message-ID: <4BF308E9.4040809@zytor.com> Date: Tue, 18 May 2010 14:38:49 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Eric Dumazet <eric.dumazet@...il.com> CC: mingo@...hat.com, linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com, tglx@...utronix.de, avi@...hat.com, linux-tip-commits@...r.kernel.org Subject: Does anyone care about gcc 3.x support for x86 anymore? Recently, we have seen an increasing number of problems with gcc 3.4 on x86; mostly due to poor constant propagation producing not just bad code but failing to properly eliminate what should be dead code. I'm wondering if there is any remaining real use of gcc 3.4 on x86 for compiling current kernels (as opposed to residual use for compiling applications on old enterprise distros.) I'm specifically not referring to other architectures here -- most of these issues have been in relation to low-level arch-specific code, and as such only affects the x86 architectures. Other architectures may very well have a much stronger need for continued support of an older toolchain. If there isn't a reason to preserve support, I would like to consider discontinue support for using gcc 3 to compile x86 kernels. If there is a valid use case, it would be good to know what it is. -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