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: <20100913182838.70aa0964@schatten.dmk.lab>
Date:	Mon, 13 Sep 2010 18:28:38 +0200
From:	Florian Mickler <florian@...kler.org>
To:	Florian Mickler <florian@...kler.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.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 Mon, 13 Sep 2010 18:21:05 +0200
Florian Mickler <florian@...kler.org> wrote:

> On Mon, 13 Sep 2010 08:56:39 -0700
> "H. Peter Anvin" <hpa@...or.com> wrote:
> 
> > On 09/13/2010 01:39 AM, Peter Zijlstra wrote:

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

What about issuing a warning like 

"gcc 3.3.3 is broken because of bug [bugdescription/url].
if you know your build is not affected by this bug do:
touch .gcc333bugfixNNNN but please be aware that you are 
not supported by the mainline kernel development comunity 
if you do"

and implementing the accompanying logic?

Cheers,
Flo
--
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/