From: Ian Lance Taylor <ian@cygnus.com>
To: ralf@uni-koblenz.de
Cc: kk@ddeorg.soft.net, gas2@cygnus.com, bfd@cygnus.com
Subject: Re: GNU linker on mips
Date: Thu, 04 Feb 1999 19:28:00 -0000 [thread overview]
Message-ID: <199902050317.WAA02402@subrogation.cygnus.com> (raw)
In-Reply-To: <19990203130347.A5244@uni-koblenz.de>
Date: Wed, 3 Feb 1999 13:03:47 +0100
From: ralf@uni-koblenz.de
On Tue, Feb 02, 1999 at 09:37:17PM -0500, Ian Lance Taylor wrote:
> I don't know of any system which uses a zero value for __start. Most
> systems protect the zero page to catch null pointer dereferences. Why
> do you expect __start to be zero? What sorts of problems are you
> seeing?
Sorry, braino on my side. I meant SHLIB_TEXT_START_ADDR, not __start. MIPS
systems typically use 0x5ffe0000, not zero and that triggered kernel bugs,
glibc bugs and some undesireable behaviour in the Linux kernel, glibc dynamic
linker and others I forgot. It did not trigger any bfd / gas / binutils bugs.
Ah. I don't know why SHLIB_TEXT_START_ADDR should be anything other
than zero. It seems to me that making it zero is a bit more natural
for the RELATIVE relocs, but I don't think MIPS ELF has a RELATIVE
reloc anyhow, and of course it shouldn't really matter anyhow.
If it is more convenient for the Linux kernel to make
SHLIB_TEXT_START_ADDR 0 for MIPS GNU/Linux, then I can't see any
reason not to do it.
Ian
prev parent reply other threads:[~1999-02-04 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 22:25 Koundinya.K
1999-02-02 18:08 ` ralf
1999-02-02 18:56 ` Ian Lance Taylor
1999-02-04 19:11 ` ralf
1999-02-04 19:28 ` Ian Lance Taylor [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=199902050317.WAA02402@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=kk@ddeorg.soft.net \
--cc=ralf@uni-koblenz.de \
/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).