Re: Back-end specific per-bfd data

[mark@codesourcery.com]

>>>>> "Ian" == Ian Lance Taylor <ian@airs.com> writes:

    Ian>    From: mark@codesourcery.com Date: Fri, 04 Jun 1999
    Ian> 08:10:31 -0700

    Ian>    There seems to be no place to put back-end specific
    Ian> per-bfd data.  That means that some of the backends have
    Ian> resulted to static data, which is surely not the right thing
    Ian> given the otherwise nicely object-oriented and reentrant
    Ian> nature of bfd.

    Ian>    There is bfd->usrdata, but that is for *application* data,
    Ian> not back-end specific data.

    Ian>    Am I missing the right hook for this?  Or, does anyone
    Ian> object to the creation of bfd->used_by_bfd analagous to the
    Ian> field of the same name in asection?

    Ian> It shouldn't be necessary.  What sort of data are you talking
    Ian> about?

    Ian> As Nick says, you can use the linker hash table to hold
    Ian> information during a link.

Thanks; it's the linker hash table that I want.  I noticed the use
of static data (mips_elf_text_section, etc.) in mips32-elf.c, and I
didn't want to perpetuate this.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com