This is the mail archive of the binutils@sourceware.org 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]
Other format: [Raw text]

Re: [PATCH][GOLD] Add ARM relocation property table.


"Doug Kwan (éæå)" <dougkwan@google.com> writes:

>> I don't like the fact that we will pay in linker startup time for
>> every linker which includes the ARM target, even if we are not
>> linking ARM. ÂThis is problematic because by default the linker
>> includes support for all targets. ÂCan we arrange for this to only be
>> constructed when the ARM target is being used?
>
> We can initialize this went we set the default target.  That should be
> MT-safe, right?

It may not be today, but it certainly should be.


>> This is a cute idea. ÂCan you think of a way to make it a bit more
>> general so that it is easier for other targets to use it?
>
> We can have a general way for all target but this is done in way so
> that a part of arm-reloc.def is almost identical to a relocation code
> table in the ARM ELF file format document.  That is intentional, I
> want it to be very easy to verify manually that the information in
> arm-reloc.def is correct.   Maybe we can use S-expression as the
> common description language but there will still be quite a bit of
> target-specific code in the analysis.  I'm open to suggestions.

Most ELF ABIs have a table just like the ARM one.  It's true that
there will always be target-specific code.

Ian


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