From: Daniel Jacobowitz <dan@debian.org>
To: Andreas Jaeger <aj@suse.de>
Cc: Guido Guenther <guido.guenther@gmx.net>, linux-mips@oss.sgi.com
Subject: Re: understanding elf_machine_load_address
Date: Sat, 8 Dec 2001 16:03:06 -0500 [thread overview]
Message-ID: <20011208160306.A385@nevyn.them.org> (raw)
In-Reply-To: <u8wuzxe8pa.fsf@gromit.moeb>
On Sat, Dec 08, 2001 at 09:52:01PM +0100, Andreas Jaeger wrote:
> 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.
>
> I just checked the MIPS R4000 Microprocessor Manual, 2nd Ed. by Joe
> Heinrich and it mentions "Unconditanally, the address of the
> instruction after the delay slot is placed in the link register, $31".
> Therefore the code is correct.
OK, thanks. Yet another thing that changed between my simulator and my
hardware :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-12-08 22:03 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
2001-12-08 20:23 ` Guido Guenther
2001-12-08 20:52 ` Andreas Jaeger
2001-12-08 21:03 ` Daniel Jacobowitz [this message]
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=20011208160306.A385@nevyn.them.org \
--to=dan@debian.org \
--cc=aj@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox