Re: [PATCH, BFD, LD, AArch64, 0/4] Add support for AArch64 BTI and PAC in the linker

[Szabolcs Nagy <Szabolcs.Nagy@arm.com>]

On 07/03/2019 15:35, Nick Clifton wrote:
>>>> The document does not appear to specify what the loader should do if
>>>> there is more than one GNU_PROPERTY_AARCh64_FEATURE_1_AND note in an
>>>> executable.  (Which would be there if the executable had been linked
>>>> by a linker that does not know how to merge multiple GNU_PROPERTY notes).
> 
>> My initial thought is that if there is more than one
>> .note.gnu.property section in the executable then the static linker
>> didn't understand the section and hence we can't assume it did any of
>> the required actions like producing different PLT sections. Hence I
>> think acting as if there were no .note.gnu.property sections present
>> at all would be a sensible choice.
> 
> Agreed.  I would just like to see this clearly specified in the documentation
> so that other linker maintainers know where they stand.

so arm decided to use the "gnu property" thing to mark elf modules.
this means the behaviour should be mostly decided by "gnu" i think.

in this case if linkers don't merge gnu property notes, that sounds
like a processor independent problem so ideally the solution would
be the same across targets. (i.e. x86_64 and aarch64 should behave
consistently)

in any case this belongs to either an os specific sysv abi
document (i.e. linux-abi maintained by H.J.Lu) or processor
specific sys v abi (arm has not published this yet) because
those describe dynamic linking behaviour. (the arm elf abi
does not cover dynamic linking)