[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: read-write locks
From: |
Paul Eggert |
Subject: |
Re: read-write locks |
Date: |
Thu, 5 Jan 2017 13:19:38 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 |
On 01/05/2017 12:47 PM, Torvald Riegel wrote:
> If gnulib really wants to make concurrency simpler, than it should look
> at higher-level abstractions first. Especially parallelism. But maybe
> it should then just wait for what C++ specifies, or contribute to that
I'm afraid this overestimates the amount of development resources we
have. Gnulib is contributed to only fitfully, and it mostly consists of
reasonably simple portability hacks. It has to be that way, otherwise
package developers won't understand and trust it. It's not a suitable
place to do concurrency research.
Concurrency with shared memory is a hard problem, and the C++ (and C)
folks have messed it up for decades. Although they may get something
reasonable eventually, in the meantime Gnulib will probably prefer to
limp along with something on the safer side of the axis.
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, (continued)
Re: C11 atomics, Bruno Haible, 2017/01/05
Re: read-write locks, Bruno Haible, 2017/01/05
Re: read-write locks, Bruno Haible, 2017/01/05
Re: read-write locks, Torvald Riegel, 2017/01/06
Re: read-write locks, Bruno Haible, 2017/01/06
Re: read-write locks, Torvald Riegel, 2017/01/06
Re: read-write locks, throttling, Bruno Haible, 2017/01/06
Re: read-write locks, throttling, Torvald Riegel, 2017/01/06
Re: read-write locks, Kamil Dudka, 2017/01/05
Re: read-write locks, Torvald Riegel, 2017/01/06