Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com, GNU C Library <libc-alpha@sourceware.cygnus.com>
Subject: Re: Clean up the mips dynamic linker
Date: Fri, 13 Jul 2001 11:26:36 +0200	[thread overview]
Message-ID: <20010713112635.A32010@bacchus.dhis.org> (raw)
In-Reply-To: <20010712182402.A10768@lucon.org>; from hjl@lucon.org on Thu, Jul 12, 2001 at 06:24:02PM -0700

On Thu, Jul 12, 2001 at 06:24:02PM -0700, H . J . Lu wrote:

> In fact, DT_MIPS_MAP_BASE_ADDR is the same as the p_addr field of the
> first loadable segment in the program header. I think it is included
> in the MIPS ABI to give the dynamic linker easy access to it.

Afair there is no requirement for loadable segments to be sorted so you'd
have to go through all the program header table to find the one with the
lowest address which isn't necessarily the first segment.

As the ABI doesn't give any guarantee that the lowest address in the segment
table is the value of DT_MIPS_BASE_ADDR I just tried to find a binary on
my IRIX boxen that violates this rule but I didn't find any.  So please,
go ahead.

> I have tested DSOs with none-zero DT_MIPS_MAP_BASE_ADDR. It works
> fine. I think it is safe to remove MAP_BASE_ADDR and old binaries
> will work with the new glibc. If someone thinks I am wrong, please
> send me a testcase to show it.

  Ralf

  reply	other threads:[~2001-07-13 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13  1:24 Clean up the mips dynamic linker H . J . Lu
2001-07-13  9:26 ` Ralf Baechle [this message]
2001-07-13 16:06   ` Ulrich Drepper
2001-07-13 18:07     ` Andreas Jaeger
2001-07-13 18:07       ` Andreas Jaeger
2001-07-13 18:17       ` H . J . Lu
2001-07-13 18:10     ` H . J . Lu
2001-07-16  6:35       ` Ulrich Drepper
2001-07-16 13:57         ` H . J . Lu
2001-07-16 22:27       ` Ulrich Drepper
2001-07-13 18:14   ` H . J . Lu
2001-07-13 19:25   ` Roland McGrath
2001-07-13 19:31     ` H . J . Lu

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=20010713112635.A32010@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=hjl@lucon.org \
    --cc=libc-alpha@sourceware.cygnus.com \
    --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