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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C8E5EDB.2070900@zytor.com>
Date:	Mon, 13 Sep 2010 10:26:51 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Peter Zijlstra <peterz@...radead.org>, florian@...kler.org,
	x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Mike Frysinger <vapier@...too.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] x86: don't compile with gcc-3.3.3

On 09/13/2010 09:33 AM, Russell King - ARM Linux wrote:
>>
>> Does it in fact still build with 3.4? I seem to recall some talk about
>> pushing the minimum version to 4.x for x86, although I can't remember
>> where..
> 
> I'm still building kernels with gcc 3.4.3 (for the ARMs which don't
> require a later compiler) or gcc 4.3.2+patches for those which do.
> 
> ARM gcc 3.4.3 is certainly noticably faster than gcc 4.3.2 even on
> x86 - and as long as ARM gcc 3.4.3 works, and there's not great pain
> in allowing it to build the arch-independent stuff, I see no reason
> to deny it across the entire kernel build.
> 
> I think we should have a minimum compiler version for the generic
> kernel, and individual minimum compiler versions for the architectures,
> so that arches can specify a higher minimum compiler version if they
> have specific problems there.

Yes, I don't think anyone has proposed bumping past 3.4 for the generic
kernel at this time.

	-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

Powered by Openwall GNU/*/Linux Powered by OpenVZ