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: Setting GNU OSABI on ARM


On 30 April 2013 14:06, nick clifton <nickc@redhat.com> wrote:

Hi Nick,

>> I was wondering if someone could help me figure out why all
>> architectures except ARM seem to set GNU OSABI when GNU indirect
>> function symbols are present?
>>
>> The below patch sets GNU OSABI on ARM and lets us run the generic
>> ifunc tests (that run on i386, x86_64, sparc and powerpc). Is there
>> some historical reason why this is a bad idea?
>
>
> I do not know of any historical reason for this.  I suspect that it was just
> an accident of the development of ifunc support.
>
> There may be a practical issue however, in that changing the EI_OSABI field
> may break OSes that expect it to be set to ELOSABI_ARM  So whilst
> technically I have no objections to the patch I think that it would be wise
> to provide a configure time option to restore the original behavior.

This was my concern, whether or not anything relies on the current
OSABI behaviour. I am not sure if anything other than Linux actually
uses STT_GNU_IFUNC either.

I'm currently implementing indirect function support for AArch64 so I
would be interested if there was any rationale to the decision, as
otherwise I will just make it use the GNU OSABI. ;-)

Thanks,

--
Will Newton
Toolchain Working Group, Linaro


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