https://sourceware.org/bugzilla/show_bug.cgi?id=16163
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Thomas,
OK, I think I can see your point now, I think that the answer to your
original question is as follows:
R_ARM_ABS12
R_ARM_ABS32
R_ARM_ABS32_NOI
R_ARM_REL32
R_ARM_REL32_NOI
R_ARM_MOVW_ABS_NC
R_ARM_MOVT_ABS
R_ARM_MOVW_PREL_NC
R_ARM_MOVT_PREL
R_ARM_THM_MOVW_ABS_NC
R_ARM_THM_MOVT_ABS
R_ARM_THM_MOVW_PREL_NC
R_ARM_THM_MOVT_PREL
This is from looking at the code in bfd/elf32-arm.c and searching for
may_become_dynamic_p.
Of course the next question is "does this mean that the linker is generating
illegal shared objects", at least as according to the AAEABI ? I am afraid
that the answer appears to be "yes", and I do not have a solution to this. I
think that it may be that established practice is that loaders need to be able
to handle these relocations, even though strictly speaking they should not.
Does this help at all ?
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
