From: Ralf Baechle <ralf@oss.sgi.com>
To: Keith Owens <kaos@melbourne.sgi.com>
Cc: Brady Brown <bbrown@ti.com>,
SGI news group <linux-mips@oss.sgi.com>,
Ulf Carlsson <ulfc@engr.sgi.com>
Subject: Re: ELF/Modutils problem
Date: Fri, 22 Sep 2000 15:31:56 +0200 [thread overview]
Message-ID: <20000922153156.A2677@bacchus.dhis.org> (raw)
In-Reply-To: <1690.969616620@ocs3.ocs-net>; from kaos@melbourne.sgi.com on Fri, Sep 22, 2000 at 08:57:00PM +1100
On Fri, Sep 22, 2000 at 08:57:00PM +1100, Keith Owens wrote:
> >On Wed, Sep 20, 2000 at 11:24:25AM +1100, Keith Owens wrote:
> >> modutils 2.3.11 includes a sanity check on the number of local symbols
> >> precisely because of this MIPS problem. I agree with you that mips gcc
> >> is violating the ELF standard, 2.3.11 just detects this and issues an
> >> error message instead of overwriting memory but gcc needs to be fixed.
> >
> >And gcc has nothing to with it so it won't need to be fixed ...
>
> Point taken, I should have said the MIPS toolchain instead of gcc.
> Something in the toolchain is generating an ELF object that does not
> follow the rules. Can we catch someone's attention to get it fixed?
Ulf Carlsson <ulfc@engr.sgi.com> is currently maintaining binutils.
Ulf, you got the bandwidth to take a look at this? After a look over the
gas code it's not obvious to my why this doesn't work on MIPS but on
all the other architectures, you probably know the internals of this beast
better than I do.
Ralf
next prev parent reply other threads:[~2000-09-22 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-20 0:03 ELF/Modutils problem Brady Brown
2000-09-20 0:24 ` Keith Owens
2000-09-21 13:36 ` Ralf Baechle
2000-09-22 9:57 ` Keith Owens
2000-09-22 13:31 ` Ralf Baechle [this message]
2000-09-22 15:23 ` Brady Brown
2000-09-23 21:06 ` Ralf Baechle
2000-09-23 22:03 ` Ulf Carlsson
2000-09-27 10:34 ` Ralf Baechle
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=20000922153156.A2677@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=bbrown@ti.com \
--cc=kaos@melbourne.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=ulfc@engr.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