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: <20100913163322.GA3819@n2100.arm.linux.org.uk>
Date:	Mon, 13 Sep 2010 17:33:22 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	florian@...kler.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.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 Mon, Sep 13, 2010 at 10:39:55AM +0200, Peter Zijlstra wrote:
> On Mon, 2010-09-13 at 10:31 +0200, florian@...kler.org wrote:
> > hpa commented on bug 16506[1] :
> > "Please note that gcc-3.3.3 is known broken on x86; gcc-3.4 is the oldest
> > version which is known to *not* be broken."
> > 
> > References: 
> > 	[0]: https://bugzilla.kernel.org/show_bug.cgi?id=16633
> > 	[1]: https://bugzilla.kernel.org/show_bug.cgi?id=16506#c28
> > 
> > If that is indeed so, we should abort the build? No?
> 
> 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.
--
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