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: farcall-section test



Sounds like we should be able to do this - and hot/cold partitioning should know that the branch might corrupt IP. On the
other hand, I can't find another way to interpret the quote about
setting "T"...

Yeah. I guess there are three options for non-function symbols:
- Don't cause a mode switch (i.e. target is arm for R_ARM_CALL and Thumb for R_ARM_THM_CALL). If you have both Arm and Thumb code jumping to the same symbol you loose.
- Interpret the T bit literally, and always treat them as ARM. If you have Thumb code you loose.
- Figure it out from mapping symbols.


The first is attractive because it matches our current behavior for intra-section branches resolved by GAS, and for "near" relocations.


Do you know how does ARM's RVCT behave in this case?


Christophe.


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