| 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: <20070821191959.GC2642@bingen.suse.de> Date: Tue, 21 Aug 2007 21:19:59 +0200 From: Andi Kleen <ak@...e.de> To: Adrian Bunk <bunk@...nel.org> Cc: Randy Dunlap <randy.dunlap@...cle.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Jarek Poplawski <jarkao2@...pl>, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: RFC: drop support for gcc < 4.0 On Tue, Aug 21, 2007 at 07:35:50PM +0200, Adrian Bunk wrote: > Obviously a gcc <= 3.4 [1], and therefore no unit-at-a-time. Actually there are widely used 3.3 variants that support unit-at-a-time (e.g. 3.3-hammer which was shipped by several distributions for some time) There are still a lot of systems around which use gcc 3.3 (less so with 3.4). Unless there's a major bug that is hard to work around I would prefer to keep it supported. Bogus warnings should be relatively harmless. > And it's becoming a real maintainance problem that not only this problem > but also other problems like some section mismatches [2] are only > present without unit-at-a-time. The unit-at-a-time output order is not defined, so even if it works with the current compiler a compiler change might still trigger that problem. So it would be better to fix those anyways. -Andi - 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