From: Richard Earnshaw <rearnsha@arm.com>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [BUG?] GCC 4.5.2 produces deprecated ARM relocation
Date: Wed, 19 Oct 2011 17:37:00 -0000 [thread overview]
Message-ID: <4E9EE764.1030506@arm.com> (raw)
In-Reply-To: <87aa93e87l.fsf@gmail.com>
On 14/10/11 19:31, Ben Gamari wrote:
> On Fri, 14 Oct 2011 18:38:26 +0100, Richard Earnshaw <rearnsha@arm.com> wrote:
>> On 14/10/11 17:40, Ben Gamari wrote:
>>> I was recently trying to test GCC's behavior in producing various types
>>> of ARM relocations. In particular, I was trying to produce an
>>> R_ARM_JUMP24 relocation, which requires veneer. It was suggested that
>>> the code most likely to produce this relocation would involve some sort
>>> of tail recursion. I wrote up a small test[1] involving interworking and
>>> tail recursion to see what the produced object might look like. To my
>>> surprise, I found that the compiler instead[2] produced the deprecated
>>> R_ARM_PLT32 relocation. Considering the deprecated state of this
>>> relocation type, should this be considered a bug? Being a linker
>>> implementer, I for one would greatly appreciate it if GCC tried to only
>>> use non-deprecated relocation types. I apologize if this has already
>>> been fixed upstream.
>>>
>>
>> The compiler doesn't produce relocations, but the assembler does. You
>> need to make sure your binutils is up-to-date.
>>
> Fair enough. I suppose that makes more sense.
>
> $ as -v
> GNU assembler version 2.21.0 (arm-linux-gnueabi) using BFD version (GNU Binutils for Ubuntu) 2.21.0.20110327
>
>
> Seems that this is the latest stable release.
You need to take that up with the binutils folks, they don't generally
hang out on this list.
R.
next prev parent reply other threads:[~2011-10-19 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 17:38 Ben Gamari
2011-10-14 20:39 ` Richard Earnshaw
2011-10-14 22:45 ` Ben Gamari
2011-10-19 17:37 ` Richard Earnshaw [this message]
[not found] <87lisglw3i.fsf@gmail.com>
[not found] ` <4EA57E62.8020802@redhat.com>
2011-10-25 14:46 ` Ben Gamari
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=4E9EE764.1030506@arm.com \
--to=rearnsha@arm.com \
--cc=bgamari.foss@gmail.com \
--cc=gcc@gcc.gnu.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).