From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <Catalin.Marinas@arm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC] ARM binutils feature churn causing kernel problems
Date: Thu, 7 Oct 2004 16:02:13 +0100 [thread overview]
Message-ID: <20041007160213.C8579@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1097057299.5332.15.camel@newt>; from adrian@humboldt.co.uk on Wed, Oct 06, 2004 at 11:08:20AM +0100
On Wed, Oct 06, 2004 at 11:08:20AM +0100, Adrian Cox wrote:
> On Tue, 2004-10-05 at 14:51, Russell King wrote:
> > On Tue, Oct 05, 2004 at 02:40:08PM +0100, Richard Earnshaw wrote:
>
> > > Looking at the output of nm -fsysv shows that currently the mapping
> > > symbols are being incorrectly typed (the EABI requires them to be
> > > STT_NOTYPE, but the previous ELF specification -- not supported by GNU
> > > utils -- required them to be typed by the data they addressed. I'll
> > > submit a patch for that shortly).
> >
> > Ugg - in that case, we need to go with the "match the name" version
> > until these changes in binutils have matured (== 2 or 3 years time.)
>
> Why does the Linux ARM ABI have to have any relation to the ARM EABI?
> The PowerPC has had two different ABIs for years, and it's not caused us
> any trouble. Can't we just leave the behaviour of binutils alone when
> configured for an arm-linux target, and put all feature churn into an
> arm-eabi target?
I'll suggest that Richard should answer this question.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-10-07 15:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 20:03 [RFC] ARM binutils feature churn causing kernel problems Russell King
2004-09-27 20:17 ` Christoph Hellwig
2004-09-27 20:35 ` Russell King
2004-09-27 20:37 ` Nicolas Pitre
2004-10-01 20:11 ` Russell King
2004-10-04 12:01 ` Catalin Marinas
2004-10-04 23:18 ` Rusty Russell
2004-10-05 11:10 ` Richard Earnshaw
2004-10-05 11:53 ` Russell King
2004-10-05 12:57 ` Richard Earnshaw
2004-10-05 13:14 ` Russell King
2004-10-05 13:40 ` Richard Earnshaw
2004-10-05 13:51 ` Russell King
2004-10-06 10:08 ` Adrian Cox
2004-10-07 15:02 ` Russell King [this message]
2004-10-12 13:15 ` Richard Earnshaw
2004-10-07 14:54 ` Russell King
2004-10-05 23:00 ` Rusty Russell
2004-10-07 12:35 ` Paulo Marques
2004-10-07 15:01 ` Russell King
2004-10-07 16:39 ` Paulo Marques
2004-10-05 13:02 ` Richard Earnshaw
2004-10-08 15:04 ` Russell King
2004-10-08 16:36 ` Paulo Marques
2004-10-08 18:14 ` Albert Cahalan
2004-10-08 19:43 ` Paulo Marques
2004-10-20 11:38 ` [PATCH] Fix ARM kernel build with permitted binutils versions Russell King
2004-10-26 22:37 ` Sam Ravnborg
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=20041007160213.C8579@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Catalin.Marinas@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=adrian@humboldt.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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.