From: ralf@uni-koblenz.de
To: Philip Blundell <pb@nexus.co.uk>, linux-mips@fnet.fr
Cc: linux@cthulhu.engr.sgi.com, linux-mips@vger.rutgers.edu
Subject: Re: Binutils 2.9.x
Date: Thu, 12 Nov 1998 00:31:03 +0100 [thread overview]
Message-ID: <19981112003103.B22798@uni-koblenz.de> (raw)
In-Reply-To: <E0zdX1R-0003xm-00@fountain.nexus.co.uk>; from Philip Blundell on Wed, Nov 11, 1998 at 09:57:09AM +0100
On Wed, Nov 11, 1998 at 09:57:09AM +0100, Philip Blundell wrote:
> Does this happen even without versioning? My experience with the ARM was that
> when we tried to start using symbol versioning it showed up various problems
> in our ELF backend (basically various invalid assumptions). All were easy to
> fix but gave symptoms like yours initially.
It's several bugs all in one. First of all somebody broke the special
handling for the .reginfo sections. We actually only have them to satisfy
the ABI, otherwise they're toxic waste since nothing uses them. Then we
have the missing support for symbol versioning. All the assert messages
I examined were caused by the dynindx field of symbol hash being set to -1
in order to force them to local symbols. Finally we have a other bugs
which account for the core dumps. So far I only have the .reginfo thing
fixed and since my knowledge about BFD internals has mostly decayed of the
long time getting the symbol versioning bugs right has proven to be quite
some work.
Ralf
prev parent reply other threads:[~1998-11-11 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-09 13:03 Binutils 2.9.x ralf
[not found] ` <E0zdX1R-0003xm-00@fountain.nexus.co.uk>
1998-11-11 23:31 ` ralf [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=19981112003103.B22798@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=pb@nexus.co.uk \
/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