[PATCH] Introduce -finstrument-functions-once

2022-05-24 Thread Eric Botcazou via Gcc-patches
Hi, some time ago we were requested to implement a -finstrument-functions-once switch in the compiler, with the semantics that the profiling functions be called only once per instrumented function. The goal was to make it possible to use it in (large) production binaries to do function-level cove

Re: [PATCH] Introduce -finstrument-functions-once

2022-06-02 Thread Richard Biener via Gcc-patches
On Tue, May 24, 2022 at 12:49 PM Eric Botcazou via Gcc-patches wrote: > > Hi, > > some time ago we were requested to implement a -finstrument-functions-once > switch in the compiler, with the semantics that the profiling functions be > called only once per instrumented function. The goal was to m

Re: [PATCH] Introduce -finstrument-functions-once

2022-06-13 Thread Eric Botcazou via Gcc-patches
> So that also applies to > > "... and the second profiling function is called before the exit > +corresponding to this first entry" > > specifically "corresponding to this first entry"? As if the second > entry exits first will that call the second profiling function or will > it really be the

Re: [PATCH] Introduce -finstrument-functions-once

2022-06-13 Thread Richard Biener via Gcc-patches
On Mon, Jun 13, 2022 at 11:46 AM Eric Botcazou wrote: > > > So that also applies to > > > > "... and the second profiling function is called before the exit > > +corresponding to this first entry" > > > > specifically "corresponding to this first entry"? As if the second > > entry exits first wi