From: Nick Clifton <nickc@redhat.com>
To: Gary Partis <Gary@partis.co.uk>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Linker --fix-v4bx problem
Date: Thu, 27 Feb 2020 16:06:00 -0000 [thread overview]
Message-ID: <4315be13-43cf-970f-8e07-08d0a34c15b1@redhat.com> (raw)
In-Reply-To: <6773ED2626D769428AEACF6C2B03437185F2671E@SERVER.partis.local>
Hi Gary,
> I am using GNU ld version 2.31.1 to target ARMv3 (ARM610/710) processors. Primarily, GCC's libgcc contains "BX LR" instructions which we want changed to "MOV PC,LR" so to be compatible with older processors, but after running the linker with the "--fix-vxb4" directive the BX instructions are still there (we use objdump to disassemble the resultant ELF file to check).
>
> Are we missing something really obvious or is the "--fix-v4bx" directive broken in some way?
It could be either situation. Please can you file a bug report here, and include a test case:
https://sourceware.org/bugzilla/
Thanks.
Cheers
Nick
next prev parent reply other threads:[~2020-02-27 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 16:34 Gary Partis
2020-02-27 16:06 ` Nick Clifton [this message]
2020-02-29 19:39 ` ***UNCHECKED*** " Gary Partis
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=4315be13-43cf-970f-8e07-08d0a34c15b1@redhat.com \
--to=nickc@redhat.com \
--cc=Gary@partis.co.uk \
--cc=binutils@sourceware.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).