From: Peter Zijlstra <peterz@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: mingo@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH 1/2] x86: Force asm-goto
Date: Tue, 20 Mar 2018 16:50:36 +0100 [thread overview]
Message-ID: <20180320155036.GU4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180320094554.2bc49dea@lwn.net>
On Tue, Mar 20, 2018 at 09:45:54AM -0600, Jonathan Corbet wrote:
> On Mon, 19 Mar 2018 16:41:25 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > A primary prerequisite for this is of course that the compiler
> > supports asm-goto. This effecively lifts the minimum GCC version to
> > build an x86 kernel to gcc-4.5.
>
> Given that, how about a patch to Documentation/Changes to reflect the new
> reality? It's not in RST yet, so you should be able to go there without
> ill effect :)
That thing says:
GCC
---
The gcc version requirements may vary depending on the type of CPU in your
computer. jon
Which is still entirely accurate. And afaik the 3.2 minimum listed there
still works for !x86.
next prev parent reply other threads:[~2018-03-20 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 15:41 [PATCH 0/2] x86: Mandate asm-goto support Peter Zijlstra
2018-03-19 15:41 ` [PATCH 1/2] x86: Force asm-goto Peter Zijlstra
2018-03-19 19:57 ` Thomas Gleixner
2018-03-19 20:13 ` Peter Zijlstra
2018-03-20 10:00 ` [tip:x86/build] " tip-bot for Peter Zijlstra
2018-03-27 16:43 ` [PATCH 1/2] " Anders Roxell
2018-03-20 15:45 ` Jonathan Corbet
2018-03-20 15:50 ` Peter Zijlstra [this message]
2018-03-20 18:44 ` Jonathan Corbet
2018-03-22 12:10 ` Pavel Machek
2018-03-19 15:41 ` [PATCH 2/2] x86: Remove FAST_FEATURE_TESTS Peter Zijlstra
2018-03-20 10:01 ` [tip:x86/build] " tip-bot for Peter Zijlstra
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=20180320155036.GU4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).