From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] arm: fix cfi errors with newer binutils
Date: Fri, 06 Jan 2012 11:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1201061151020.14524@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201201060149.25299.vapier@gentoo.org>
On Fri, 6 Jan 2012, Mike Frysinger wrote:
> On Tuesday 03 January 2012 12:44:19 Joseph S. Myers wrote:
> > On Tue, 3 Jan 2012, Mike Frysinger wrote:
> > > so ARM cores older than armv4t are no longer supported (e.g. StrongARMs)
> > > ? :(
> >
> > I believe you can use ARMv4 cores with EABI via the
> > --fix-v4bx-interworking linker option (building code that works on v4 and
> > is interworking-safe on v4T). (You may be able to link with plain
> > --fix-v4bx, but the resulting binaries and shared libraries then wouldn't
> > be interworking safe if run on a newer system, unless that newer system
> > is v7.)
>
> nice. i wonder if gcc should automatically utilize this when given -march
> armv4 or lower ?
It looks like the relevant assembler spec (so that the instruction is
accepted and has the R_ARM_V4BX relocation generated that the linker needs
to fix them up) is already there for all EABI targets (in bpabi.h and not
overridden by individual targets), but the linker spec is enabled for
bare-metal but not GNU/Linux (I suppose because there isn't a
one-size-fits-all answer for which of the two linker options you might
want to use on GNU/Linux).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2012-01-06 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 22:45 Mike Frysinger
2012-01-03 16:37 ` Joseph S. Myers
2012-01-03 17:31 ` Mike Frysinger
2012-01-03 17:44 ` Joseph S. Myers
2012-01-06 6:49 ` Mike Frysinger
2012-01-06 11:56 ` Joseph S. Myers [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=Pine.LNX.4.64.1201061151020.14524@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).