From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Cort Dougan <cort@ppc.kernel.org>, binutils@sourceware.cygnus.com
Subject: Re: ppc-linux gcc configury patch
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <4.2.0.56.19990608113015.04a08400@mail.lauterbach.com> (raw)
In-Reply-To: <19990607174358.A1945@cygnus.com>
At 02:43 08.06.99 , Richard Henderson wrote:
> > If there's no compatibility problem with glibc-1.99, changing
> > TEXT_START_ADDR for elf32ppc would be enough, the values in
> > there are already Linux-specific.
>
>Well, not quite.
>
>Mon Jun 16 19:18:21 1997 Geoff Keating <geoffk@ozemail.com.au>
>
> * emulparams/elf32ppc.sh (TEXT_START_ADDR): The ABI says `A
> program base of 0x02000000 is recommended...' because otherwise
> shared libraries are less efficient.
>
>As such there may well be other elf32ppc users (embedded systems
>folks mostly, so I don't know how much it matters in practice)
>that would prefer to have the default remain unchanged.
Uhm, you left out the most important part of this ChangeLog entry, it
continues as follows:
We use 0x01800000 because otherwise it's impossible to branch to
location 0, for instance if you have an undefined weak symbol.
So it _is_ already Linux/PPC specific.
>Given that I do not expect a native Linux system to have more than
>one of elf32ppc or elf32ppclinux installed, I don't see what
>relevance your LIB_PATH argument is.
See Dan's bugreport on binutils, that's exactly what happens. Without
special measurements it's impossible to bootstrap gcc-2.95 now. With the
old binutils the stage compilers will barf, with the new binutils
egcs-1.1.2 will barf :-(. Wouldn't it be better to split out an
elf32ppceabi if an embedded guy ever requests it? I would assume embedded
doesn't need a native library search patch anyway.
Franz.
next parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99060800354700.01456@ns1102.munich.netsurf.de>
[not found] ` <19990604124947.A19158@attis.cs.nmt.edu>
[not found] ` <19990607174358.A1945@cygnus.com>
1999-07-01 0:00 ` Franz Sirl [this message]
1999-07-01 0:00 ` Richard Henderson
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=4.2.0.56.19990608113015.04a08400@mail.lauterbach.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=binutils@sourceware.cygnus.com \
--cc=cort@ppc.kernel.org \
--cc=rth@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).