Re: [patch] improve entry/exit instrumentation wrt trampolines

2018-06-22 Thread Olivier Hainque
Hi Jeff, > On 22 Jun 2018, at 18:13, Jeff Law wrote: > >>> * gimplify.c (gimplify_function_tree): Prevent creation >>> of a trampoline for the address of the current function >>> passed to entry/exit instrumentation hooks. > I was a little concerned about the TREE_NO_TRAMPOLINE bit,

Re: [patch] improve entry/exit instrumentation wrt trampolines

2018-06-22 Thread Jeff Law
On 06/22/2018 09:47 AM, Olivier Hainque wrote: > > >> On 22 Jun 2018, at 17:44, Olivier Hainque wrote: > >> Receiving the actual function address would seem more >> useful for function-instrumentation purposes, and this >> patch adjusts the compiler to do that instead. >> >> 2018-06-22 Olivier

Re: [patch] improve entry/exit instrumentation wrt trampolines

2018-06-22 Thread Olivier Hainque
> On 22 Jun 2018, at 17:44, Olivier Hainque wrote: > Receiving the actual function address would seem more > useful for function-instrumentation purposes, and this > patch adjusts the compiler to do that instead. > > 2018-06-22 Olivier Hainque > > * gimplify.c (gimplify_function_tree

[patch] improve entry/exit instrumentation wrt trampolines

2018-06-22 Thread Olivier Hainque
Hello, Execution of the example program below shows that when a nested function is called by way of a stack trampoline, the -finstrument-functions hooks receive the address of the trampoline as the "this function" parameter. Receiving the actual function address would seem more useful for functio