On Wed, 13 Nov 2013, neleai at seznam dot cz wrote:
> Why did you jump from dlopening to static linking? Dynamic linking would
> work and if there is concern that user does not have one we could
> provide a stub implementation and function to test if we deal with stub
> or real one.
I don't think default dlopening libgcc_s from libc at startup is desirable
on performance grounds (most programs will never need it), whereas from
libpthread it's likely to be less significant.
On Wed, 13 Nov 2013, neleai at seznam dot cz wrote:
> Why did you jump from dlopening to static linking? Dynamic linking would
> work and if there is concern that user does not have one we could
> provide a stub implementation and function to test if we deal with stub
> or real one.
I don't think default dlopening libgcc_s from libc at startup is desirable
on performance grounds (most programs will never need it), whereas from
libpthread it's likely to be less significant.