[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100913204244.55524e22@schatten.dmk.lab>
Date: Mon, 13 Sep 2010 20:42:44 +0200
From: Florian Mickler <florian@...kler.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: 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 10:25:43 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:
> On 09/13/2010 09:28 AM, Florian Mickler wrote:
> >
> > 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?
> >
>
> URK.
>
> The workload of maintaining that crap would be astonishing, especially
> for something at the tail end of supportable.
>
> I don't think that is even remotely realistic.
>
> -hpa
I can imagine that even without having expirienced anything alike :)
Should I then resend this RFC-Patch updated to abort the x86-build for
gcc -lt 3.4?
Regards,
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/
Powered by blists - more mailing lists