From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Florian Mickler <florian@mickler.org>,
Peter Zijlstra <peterz@infradead.org>,
Mike Frysinger <vapier@gentoo.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/5] Disallow building with gcc < 3.4
Date: Mon, 13 Sep 2010 22:52:43 +0100 [thread overview]
Message-ID: <20100913215243.GA12464@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1284408880-14414-2-git-send-email-hpa@linux.intel.com>
On Mon, Sep 13, 2010 at 01:14:36PM -0700, H. Peter Anvin wrote:
> Disallow building the generic kernel code with gcc < 3.4. Earlier
> versions of gcc have known problems, and it appears that anyone who
> genuinely needs gcc 3.x can use gcc 3.4 at this point.
>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Reviewed-by: Russell King <rmk+kernel@arm.linux.org.uk>
next prev parent reply other threads:[~2010-09-13 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 20:14 [RFC PATCH 0/5] Bump gcc minimum version to 3.4, 4.1 for x86 H. Peter Anvin
2010-09-13 20:14 ` [PATCH 1/5] Disallow building with gcc < 3.4 H. Peter Anvin
2010-09-13 21:52 ` Russell King - ARM Linux [this message]
2010-09-13 20:14 ` [PATCH 2/5] x86, gcc: Disallow building Linux/x86 with gcc 3.x/4.0 H. Peter Anvin
2010-09-13 20:14 ` [PATCH 3/5] x86, cpu: Remove gcc 3.x workarounds in <asm/cpufeature.h> H. Peter Anvin
2010-09-13 20:14 ` [PATCH 4/5] x86, mem: Remove gcc < 4.1 support code for memcpy() H. Peter Anvin
2010-09-13 20:14 ` [PATCH 5/5] x86, bitops: Remove gcc < 4.1 workaround H. Peter Anvin
2010-09-14 0:11 ` [RFC PATCH 0/5] Bump gcc minimum version to 3.4, 4.1 for x86 Brian Gerst
2010-09-15 22:24 ` 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=20100913215243.GA12464@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=florian@mickler.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vapier@gentoo.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.