[GOLD][PATCH] Added support for R_ARM_V4BX relocation (with interworking)

[Doug Kwan (關振德)]

2010/1/18 Viktor Kutuzov <vkutuzov@accesssoftek.com>:

> [VK] There is only one important (on my sight) reason to use only one glue owner stub table -- I'm not sure that it is not a right behavior to expand the non-executable segments with the veneer code if those segments have the V4BX relocations. What do you think?

If you think it is okay to put a R_ARM_V4BX in a non-executable
section, why is it a problem to put the stub table in such a section?
I am still not sure why you want to put R_ARM_V4BX in a data section
or if this is a right thing to do.

>> There is even no guarantee that the glue owner stub table and the section using it will be in memory at the same time if overlays is allowed
> yes, this might be a point against of my suggestion. ok.
>