linux-kernel - Re: [RFC PATCH] x86: don't compile with gcc-3.3.3

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: <4C8E49B7.7040104@zytor.com>
Date:	Mon, 13 Sep 2010 08:56:39 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	florian@...kler.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Russell King <linux@....linux.org.uk>,
	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 01:39 AM, 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..

It does indeed still build with 3.4, although it is giving us a bunch of
headaches to *make it so*, and I would personally be really glad if the
consensus is we can just axe it.

The only reason to not abort the build for gcc 3.3.3 is that soem
"enterprise" distros have been shipping gcc 3.3.3 with backported fixes
from 3.4, which of course still identifies themselves as gcc 3.3.3, and
so technically it is iompossioble to tell if any particular "gcc 3.3.3"
is actually broken or not.

However, as far as I can tell, most of the people who build current x86
kernels with gcc 3.x are people who are testing building current kernels
with gcc 3.x.  Some of the embedded systems are different, because for
some strange reasons most of the embedded world seem stuck on gcc 3.4 or so.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/