On Thu, Oct 5, 2017 at 9:11 AM, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 09:01:14 -0700
> Thomas Garnier wrote:
>
>> On Thu, Oct 5, 2017 at 6:06 AM, Steven Rostedt wrote:
>> > On Wed, 4 Oct 2017 14:19:56 -0700
>> > Thomas Garnier wrote:
>> >
>> >> When using -fPIE/PIC with function tracing,
On Thu, Oct 5, 2017 at 6:06 AM, Steven Rostedt wrote:
> On Wed, 4 Oct 2017 14:19:56 -0700
> Thomas Garnier wrote:
>
>> When using -fPIE/PIC with function tracing, the compiler generates a
>> call through the GOT (call *__fentry__@GOTPCREL). This instruction
>> takes 6 bytes instead of 5 on the u
When using -fPIE/PIC with function tracing, the compiler generates a
call through the GOT (call *__fentry__@GOTPCREL). This instruction
takes 6 bytes instead of 5 on the usual relative call.
With this change, function tracing supports 6 bytes on traceable
function and can still replace relative ca
On Thu, 5 Oct 2017 09:01:14 -0700
Thomas Garnier wrote:
> On Thu, Oct 5, 2017 at 6:06 AM, Steven Rostedt wrote:
> > On Wed, 4 Oct 2017 14:19:56 -0700
> > Thomas Garnier wrote:
> >
> >> When using -fPIE/PIC with function tracing, the compiler generates a
> >> call through the GOT (call *__fen
On Wed, 4 Oct 2017 14:19:56 -0700
Thomas Garnier wrote:
> When using -fPIE/PIC with function tracing, the compiler generates a
> call through the GOT (call *__fentry__@GOTPCREL). This instruction
> takes 6 bytes instead of 5 on the usual relative call.
>
> With this change, function tracing sup
