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

[Viktor Kutuzov <vkutuzov at accesssoftek dot com>]

ok, understood. I'll add a stub in the same section.

Viktor.
________________________________________
From: Doug Kwan (關振紱) [dougkwan@google.com]
Sent: Monday, January 18, 2010 5:34 PM
To: Viktor Kutuzov
Cc: binutils@sourceware.org
Subject: Re: [GOLD][PATCH] Added support for R_ARM_V4BX relocation (with        interworking)

I have not doubt you can put any relocation in any section.   The
R_ARM_V4BX is used with an instruction, so what is the problem of
adding the a stub in the same section?

-Doug

2010/1/18 Viktor Kutuzov <vkutuzov@accesssoftek.com>:
> Sorry, I wanted to say -- "I'm not sure that it is a right behaviour ...". Sorry once again.
>
>>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.
>
> Technically, it is possible to put R_ARM_V4BX in a data section. I don't wanna say what it is a regular thing, but it is allowed to write something like that:
> ...
>  .section .my_data, "aw"
>      ldr r0, .LBX
>      bx  r0                @ << R_ARM_V4BX
>  .LBX:
>     nop
>     ...
>  .end
>
> and AS will generate an object file with R_ARM_V4BX in the .my_data section and we should handle this relocation I suppose.
>
> Viktor.
>
>
> ________________________________________
> From: Doug Kwan (關振紱) [dougkwan@google.com]
> Sent: Monday, January 18, 2010 5:01 PM
> To: Viktor Kutuzov
> Cc: binutils@sourceware.org
> Subject: Re: [GOLD][PATCH] Added support for R_ARM_V4BX relocation (with        interworking)
>
> 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.
>>