From: Andreas Jaeger <aj@suse.de>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Guido Guenther <guido.guenther@gmx.net>, linux-mips@oss.sgi.com
Subject: Re: understanding elf_machine_load_address
Date: Sat, 08 Dec 2001 20:42:32 +0100 [thread overview]
Message-ID: <u8g06lfqhj.fsf@gromit.moeb> (raw)
In-Reply-To: <20011208114713.A20432@nevyn.them.org> (Daniel Jacobowitz's message of "Sat, 8 Dec 2001 11:47:13 -0500")
Daniel Jacobowitz <dan@debian.org> writes:
> On Sat, Dec 08, 2001 at 04:18:53PM +0100, Andreas Jaeger wrote:
>> > " bltzal $0, here\n"
>> > " nop\n"
>> > "here: subu %0, $31, %0\n"
>>
>> Subtract shared address of "here" from address of "here" at build time
>> - and you know at which address byte 0 of the shared library is
>> loaded.
>
> Wait a second. Does bltzal fill in $31 even on a not-taken branch?
> Because bltzal $0 should never be taken. My handy MIPS reference and
> SPIM seem to agree that it won't fill in $31.
That's what I've asked myself also when fixing the dynamic linker.
But Ralf convinced me that $31 will get filled in (and I verified that
it did) - otherwise the dynamic linker would not work on any system at
all.
But it might be worth checking if Guido notices a problem.
Btw. could anybody send me a patch documenting this instruction so
that next time everybody knows directly what's going on?
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-12-08 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 14:11 understanding elf_machine_load_address Guido Guenther
2001-12-08 15:18 ` Andreas Jaeger
2001-12-08 16:37 ` Guido Guenther
2001-12-08 16:47 ` Daniel Jacobowitz
2001-12-08 19:42 ` Andreas Jaeger [this message]
2001-12-08 20:23 ` Guido Guenther
2001-12-08 20:52 ` Andreas Jaeger
2001-12-08 21:03 ` Daniel Jacobowitz
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=u8g06lfqhj.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=dan@debian.org \
--cc=guido.guenther@gmx.net \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.