From: Florian Mickler <florian@mickler.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Russell King <linux@arm.linux.org.uk>,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86: don't compile with gcc-3.3.3
Date: Mon, 13 Sep 2010 20:42:44 +0200 [thread overview]
Message-ID: <20100913204244.55524e22@schatten.dmk.lab> (raw)
In-Reply-To: <4C8E5E97.6070908@zytor.com>
On Mon, 13 Sep 2010 10:25:43 -0700
"H. Peter Anvin" <hpa@zytor.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
next prev parent reply other threads:[~2010-09-13 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 8:31 [RFC PATCH] x86: don't compile with gcc-3.3.3 florian
2010-09-13 8:39 ` Peter Zijlstra
2010-09-13 15:56 ` H. Peter Anvin
2010-09-13 16:21 ` Florian Mickler
2010-09-13 16:28 ` Florian Mickler
2010-09-13 17:25 ` H. Peter Anvin
2010-09-13 18:42 ` Florian Mickler [this message]
2010-09-13 20:00 ` H. Peter Anvin
2010-09-13 20:03 ` Florian Mickler
2010-09-13 16:33 ` Russell King - ARM Linux
2010-09-13 17:26 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100913204244.55524e22@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vapier@gentoo.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox