This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Thread-, Signal- and Cancellation-safety documentation
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Rich Felker <dalias at aerifal dot cx>
- Cc: Torvald Riegel <triegel at redhat dot com>, libc-alpha at sourceware dot org
- Date: Sun, 02 Jun 2013 19:47:23 -0300
- Subject: Re: Thread-, Signal- and Cancellation-safety documentation
- References: <1368788184 dot 3054 dot 3161 dot camel at triegel dot csb> <orehd3h2j4 dot fsf at livre dot home> <1369588322 dot 16968 dot 2933 dot camel at triegel dot csb> <orip20qzua dot fsf at livre dot home> <1369936586 dot 16968 dot 9405 dot camel at triegel dot csb> <orehcmq122 dot fsf at livre dot home> <orehclih8s dot fsf at livre dot home> <ory5atgkyr dot fsf at livre dot home> <20130602143136 dot GM20323 at brightrain dot aerifal dot cx> <orppw4h1v1 dot fsf at livre dot home> <20130602215932 dot GC29800 at brightrain dot aerifal dot cx>
On Jun 2, 2013, Rich Felker <dalias@aerifal.cx> wrote:
> use of the self-pipe trick for signal handling may make the issue come
> into play for multi-threaded apps too.
Sure, even linuxthreads used that internally.
> POSIX requires actual shared memory. An implementation that fakes it
> is not conforming.
We're all screwed, then, because NUMA is hardly actual shared memory :-)
XSHM is optional, and the phrasing of memory synchronization suggest
allowance for memory not being actually shared. Where is this
requirement you mention stated?
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer