This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: mips gas is horribly broken


"H . J . Lu" <hjl@lucon.org> writes:

> > I would say that the main problem is that it assumes that the object
> > file contents are valid, and that the relocation addend is valid for a
> > relocateable object file.
> 
> What is the best way to provide necessary information to
> bfd_install_relocation? I am thinking to add a new field,
> addend_info, to reloc_cache_entry. We initialize it to 0
> and each backend can use it to pass the necessay information
> to bfd_install_relocation.

bfd_install_relocation has all the information that it needs.  The
problem is that it does the wrong thing.

If you want to incrementally improve it, I recommend that you consider
the section ``BFD relocation future'' which I wrote in
bfd/doc/bfdint.texi.

This is not a place for quick hacks.  Quick hacks got us where we are
today.  This is place for a designed approach.  Write the design, put
it out for comments, then implement it.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]