From: Daniel Jacobowitz <drow@false.org>
To: johnmc@sidsa.es
Cc: Richard.Earnshaw@arm.com, binutils@sources.redhat.com
Subject: Re: plt for arm gnu thumb
Date: Tue, 18 Apr 2006 13:10:00 -0000 [thread overview]
Message-ID: <20060418130617.GA10461@nevyn.them.org> (raw)
In-Reply-To: <4385.195.53.86.158.1145361498.squirrel@webmail>
On Tue, Apr 18, 2006 at 01:58:18PM +0200, johnmc@sidsa.es wrote:
> hello
>
>
> I have just finished a shared library system using the gnu tools for a
> system using arm thumb code but I have found that there is a problem in
> that the plt is produced for arm code and it does not work correctly .
> question - can I force the gnu tools to produce thumb code plt.
What is the actual problem?
The PLT will always be in 32-bit instructions, but the linker should
arrange for things to work for PLT calls from Thumb also.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-18 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 13:06 johnmc
2006-04-18 13:10 ` Daniel Jacobowitz [this message]
2006-04-18 15:14 ` johnmc
2006-04-18 15:45 ` Richard Earnshaw
2006-04-18 15:49 ` Daniel Jacobowitz
2006-04-18 16:01 ` Richard Earnshaw
2006-04-18 16:49 ` Daniel Jacobowitz
[not found] ` <4596.195.53.86.158.1145376723.squirrel@webmail>
[not found] ` <20060418203900.GA23304@nevyn.them.org>
[not found] ` <1178.195.53.86.158.1145458815.squirrel@webmail>
[not found] ` <20060419150716.GA13655@nevyn.them.org>
2006-04-20 14:32 ` johnmc
2006-04-20 14:38 ` Richard Earnshaw
[not found] ` <1507.195.53.86.158.1145536917.squirrel@webmail>
[not found] ` <1145538390.16122.39.camel@pc960.cambridge.arm.com>
[not found] ` <1576.195.53.86.158.1145540607.squirrel@webmail>
[not found] ` <1145541382.16122.62.camel@pc960.cambridge.arm.com>
2006-04-24 18:23 ` johnmc
2006-04-25 17:19 ` Nick Clifton
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=20060418130617.GA10461@nevyn.them.org \
--to=drow@false.org \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sources.redhat.com \
--cc=johnmc@sidsa.es \
/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).