Re: [PATCH] Memory fencing problem in pthread cancellation

[Jeff Law <law at redhat dot com>]

On 01/14/2013 08:50 PM, Rich Felker wrote:
> The cleanest and most correct way to fix this is to add libgcc_s.so to
> the DT_NEEDED for libpthread.so and remove the silly dynamic loading
> code. Then no global state exists and everything just works. This
> would also eliminate the unfortunate, really nasty situation whereby
> pthread_cancel can abort the whole application due to failure to load
> libgcc_s.so.
The decision to use dynamic loading vs DT_NEEDED was made well before I 
began participating in glibc development;  I do not know the reasons one 
approach was chosen over the other. Nor do I feel qualified to argue for 
either the status quo or for a re-evaluation of that decision.

If Roland, Carlos, Joseph, etc want to revisit that issue, that's fine 
with me.  If they don't want to revisit that decision, that's fine too.

jeff