On Tue, Apr 2, 2024 at 10:03 AM Jan Hubicka wrote:
>
> > > I am bit worried about commonly used functions getting "infected" by
> > > being called once from ifunc resolver. I think we only use thread local
> > > storage for indirect call profiling, so we may just disable indirect
> > > call profi
> > I am bit worried about commonly used functions getting "infected" by
> > being called once from ifunc resolver. I think we only use thread local
> > storage for indirect call profiling, so we may just disable indirect
> > call profiling for these functions.
>
> Will change it.
>
> > Also the
On Tue, Apr 2, 2024 at 7:50 AM Jan Hubicka wrote:
>
> > On Tue, Mar 5, 2024 at 1:45 PM H.J. Lu wrote:
> > >
> > > We can't instrument an IFUNC resolver nor its callees as it may require
> > > TLS which hasn't been set up yet when the dynamic linker is resolving
> > > IFUNC symbols.
> > >
> > > Ad
> On Tue, Mar 5, 2024 at 1:45 PM H.J. Lu wrote:
> >
> > We can't instrument an IFUNC resolver nor its callees as it may require
> > TLS which hasn't been set up yet when the dynamic linker is resolving
> > IFUNC symbols.
> >
> > Add an IFUNC resolver caller marker to cgraph_node and set it if the
On Tue, Mar 5, 2024 at 1:45 PM H.J. Lu wrote:
>
> We can't instrument an IFUNC resolver nor its callees as it may require
> TLS which hasn't been set up yet when the dynamic linker is resolving
> IFUNC symbols.
>
> Add an IFUNC resolver caller marker to cgraph_node and set it if the
> function is
We can't instrument an IFUNC resolver nor its callees as it may require
TLS which hasn't been set up yet when the dynamic linker is resolving
IFUNC symbols.
Add an IFUNC resolver caller marker to cgraph_node and set it if the
function is called by an IFUNC resolver. Update tree_profiling to skip
