On 4/15/19 10:31 AM, Joao Moreira wrote:
>
>
> On 4/12/19 1:19 PM, Jeff Law wrote:
>> On 4/11/19 11:18 AM, Joao Moreira wrote:
>>> When -fpatchable-relocation-entry is used, gcc places nops on the
>>> prologue of each compiled function and creates a section named
>>> __patchable_function_entries
On 4/12/19 1:19 PM, Jeff Law wrote:
On 4/11/19 11:18 AM, Joao Moreira wrote:
When -fpatchable-relocation-entry is used, gcc places nops on the
prologue of each compiled function and creates a section named
__patchable_function_entries which holds relocation entries for the
positions in which
On 4/11/19 11:18 AM, Joao Moreira wrote:
> When -fpatchable-relocation-entry is used, gcc places nops on the
> prologue of each compiled function and creates a section named
> __patchable_function_entries which holds relocation entries for the
> positions in which the nops were placed. As is, gcc c
When -fpatchable-relocation-entry is used, gcc places nops on the
prologue of each compiled function and creates a section named
__patchable_function_entries which holds relocation entries for the
positions in which the nops were placed. As is, gcc creates this
section without the proper section fl
