From: "H. Peter Anvin" <hpa@zytor.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
florian@mickler.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
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 10:26:51 -0700 [thread overview]
Message-ID: <4C8E5EDB.2070900@zytor.com> (raw)
In-Reply-To: <20100913163322.GA3819@n2100.arm.linux.org.uk>
On 09/13/2010 09:33 AM, Russell King - ARM Linux wrote:
>>
>> 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.
Yes, I don't think anyone has proposed bumping past 3.4 for the generic
kernel at this time.
-hpa
prev parent reply other threads:[~2010-09-13 17:28 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
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 [this message]
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=4C8E5EDB.2070900@zytor.com \
--to=hpa@zytor.com \
--cc=florian@mickler.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.