This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] ifunc suck, use ufunc.
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Szabolcs Nagy <nsz at port70 dot net>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 25 May 2015 08:11:31 +0200
- Subject: Re: [RFC] ifunc suck, use ufunc.
- Authentication-results: sourceware.org; auth=none
- References: <20150524213858 dot GA18221 at domone> <20150525014323 dot GC26188 at port70 dot net>
On Mon, May 25, 2015 at 03:43:23AM +0200, Szabolcs Nagy wrote:
> * Ond??ej B?lka <neleai@seznam.cz> [2015-05-24 23:38:58 +0200]:
> > A main benefit would be interlibrary constant folding. Why waste cycles
> > on reinitializing constant, just save it to ufunc structure. Resolver
> > then could precompute tables to improve speed.
> >
> > As interposing these you would need to interpose resolver.
> >
> > An gcc support is not needed but we could get something with alternate
> > calling convention as passing resolver struct is common and could be
> > preserved for loops with tail calls.
> >
> > A future direction could be replace plt and linker with ufunc, it would
> > require adding function string pointer to structure and calling first
> > generic resolver to select specific resolver.
> >
> > Comments?
> >
>
> this makes memset non-async-signal-safe. (qoi issue)
>
How, could you elaborate where exactly would it cause problem with
signals? And dlsym don't count, its just implementation detail.