This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: elf_link_hash_entry vs generic_link_hash_entry
- To: Nick Clifton <nickc at cambridge dot redhat dot com>
- Subject: Re: elf_link_hash_entry vs generic_link_hash_entry
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Thu, 23 Aug 2001 09:21:40 -0700
- Cc: binutils at sources dot redhat dot com, Ian Lance Taylor <ian at zembu dot com>
- References: <si66bh2zdl.fsf@daffy.airs.com> <m3y9ocbkyw.fsf_-_@north-pole.nickc.cambridge.redhat.com>
On Wed, Aug 22, 2001 at 08:41:11AM +0100, Nick Clifton wrote:
>
> 3. Go back to the old situation where elf ports that do not provide
> their own relocation backends use the generic linker hash table
> entry structure, but add code to the other elf routines to
> detect this and fail before they try to access fields in the
> hash structure that are not there.
>
I'd like this one. How about we turn elf_hash_table into something
specific to each backend? For those targets which don't use
_bfd_elf_link_hash_table_create, it will return NULL or a fatal
bfd error.
H.J.