From: Ben Gamari <bgamari.foss@gmail.com>
To: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: Nick Clifton <nickc@redhat.com>, Richard Earnshaw <rearnsha@arm.com>
Subject: Re: [BUG?] GCC 4.5.2 produces deprecated ARM relocation
Date: Tue, 25 Oct 2011 14:46:00 -0000 [thread overview]
Message-ID: <87lis9gozc.fsf@gmail.com> (raw)
In-Reply-To: 4E9EE764.1030506@arm.com
On Mon, 24 Oct 2011 16:04:02 +0100, Nick Clifton <nickc@redhat.com> wrote:
> Hi Ben,
>
> > 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?
>
> Yes...
>
> > Being a linker
> > implementer, I for one would greatly appreciate it if GCC tried to only
> > use non-deprecated relocation types.
>
> And so you will need to repost this bug report to the gcc bug mailing
> list, since it is gcc's fault...
>
> What is happening is that GCC is producing this assembler output for the
> call to hi():
>
> bl hi(PLT)
>
> The presence of the "(PLT)" instructs GAS to produce the deprecated
> ARM_PLT32 reloc. (See the ARM specific portion of the GAS documentation
> for a mention of this).
>
> GCC is adding this suffix because the -fPIC flag enables NEED_PLT_RELOC
> (see gcc/config/arm/elf.h). Why elf.h is doing this I am not sure -
> backwards compatibility maybe ? Anyway it is GCC that needs fixing, not
> GAS.
>
> Cheers
> Nick
next parent reply other threads:[~2011-10-25 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lisglw3i.fsf@gmail.com>
[not found] ` <4EA57E62.8020802@redhat.com>
2011-10-25 14:46 ` Ben Gamari [this message]
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
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=87lis9gozc.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=rearnsha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).