From: Nicolas Pitre <nico@fluxnic.net>
To: Rob Landley <rob@landley.net>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Måns Rullgård" <mans@mansr.com>, "Andrew Morton" <akpm@osdl.org>,
"Trivial patch monkey" <trivial@kernel.org>,
"Catalin Marinas" <Catalin.Marinas@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pavel Machek" <pavel@ucw.cz>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: new binutils needed for arm in 3.12-rc1
Date: Tue, 24 Sep 2013 22:07:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1309242158340.312@syhkavp.arg> (raw)
In-Reply-To: <1380071607.1974.78@driftwood>
On Tue, 24 Sep 2013, Rob Landley wrote:
> On 09/24/2013 04:48:00 PM, Russell King - ARM Linux wrote:
> > Now, if you feel strongly about this, we _could_ introduce a
> > CONFIG_OLD_BINUTILS and give everyone their cake - but it will be
> > fragile. Not everyone will remember to get that right, because they'll
> > be using the later binutils. Also, we already have an excessive number
> > of potential breakage-inducing options and we certainly don't need
> > another.
>
> I'm doing the regression testing either way, on several different
> architectures. (Although I tend to to only really do a thorough job quarterly
> when a new kernel comes out and it's time to make it work.) So I'm going to be
> doing something locally like this anyway, and if a CONFIG_OLD_BINUTILS is
> acceptable I might as well push it upstream.
If you are convinced you have no choice but to stick to old binutils,
I'd strongly suggest you make your binutils compatible with newer
instruction syntax instead of making the kernel more complex. This is
more in line with being future proof rather than stuck into the past.
It could be as simple as making gas accept an extra argument for
instructions like dsb and just ignoring it.
Nicolas
next prev parent reply other threads:[~2013-09-25 2:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 9:30 3.12-rc1: no longer compiles for Nokia n900 (omap based) Pavel Machek
2013-09-19 9:36 ` Will Deacon
2013-09-19 9:57 ` Pavel Machek
2013-09-23 23:59 ` new binutils needed for arm in 3.12-rc1 Pavel Machek
2013-09-24 2:13 ` Rob Landley
2013-09-24 12:11 ` Måns Rullgård
2013-09-24 21:23 ` Rob Landley
2013-09-24 21:48 ` Russell King - ARM Linux
2013-09-25 1:13 ` Rob Landley
2013-09-25 2:07 ` Nicolas Pitre [this message]
2013-09-25 15:23 ` Rob Landley
2013-09-25 15:52 ` Måns Rullgård
2013-09-26 0:10 ` Rob Landley
2013-09-26 22:24 ` Måns Rullgård
2013-09-25 16:13 ` Nicolas Pitre
2013-09-26 22:48 ` Rob Landley
2013-09-27 19:41 ` Pavel Machek
2013-09-28 8:43 ` Pavel Machek
2013-09-25 20:44 ` Russell King - ARM Linux
2013-09-25 20:49 ` Måns Rullgård
2013-09-26 22:50 ` Rob Landley
2013-09-26 7:18 ` Geert Uytterhoeven
2013-09-28 9:03 ` richard -rw- weinberger
2013-09-24 2:20 ` Rob Landley
2013-09-19 9:44 ` 3.12-rc1: no longer compiles for Nokia n900 (omap based), display no longer works Pavel Machek
2013-09-19 18:47 ` Aaro Koskinen
2013-09-26 0:23 ` Pavel Machek
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=alpine.LFD.2.03.1309242158340.312@syhkavp.arg \
--to=nico@fluxnic.net \
--cc=Catalin.Marinas@arm.com \
--cc=akpm@osdl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mans@mansr.com \
--cc=pavel@ucw.cz \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--cc=trivial@kernel.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®