signals and _REENT

[Jeff Johnston]

Actually I did miss something.  Since we are using the global list,
we have to thread protect it with locking and unlocking.  The normal way would be
to add two new locks: __sigfunc_lock_acquire() and __sigfunc_lock_release() which
are needed if not single threaded.  This will cause some breakage for builds that
use threads until they define these locks.  Perhaps a single global reent lock might
be helpful.

-- Jeff J.

----- Original Message -----
From: "Freddie Chopin" <freddie_chopin@op.pl>
To: newlib@sourceware.org
Sent: Thursday, February 26, 2015 4:03:59 PM
Subject: Re: signals and _REENT

On 02/26/2015 08:39 PM, Jeff Johnston wrote:
> Here is patch as mentioned.  Did I miss anything?

I didn't spot anything wrong with your patch - it's exactly what I had 
in mind.

Regards,
FCh