This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Add atomic operations required by the new condition variable.
- From: Torvald Riegel <triegel at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Wed, 15 Jun 2016 10:49:14 +0200
- Subject: Re: [PATCH] Add atomic operations required by the new condition variable.
- Authentication-results: sourceware.org; auth=none
- References: <1464217452 dot 1779 dot 67 dot camel at localhost dot localdomain> <f11ac885-e099-0cc5-4a6a-7b02127bfcb8 at redhat dot com> <1464347799 dot 17104 dot 113 dot camel at localhost dot localdomain> <c6b24203-8683-8163-7a7f-019365fdfc9b at redhat dot com> <1465928498 dot 19633 dot 113 dot camel at localhost dot localdomain> <97cfa451-72b3-3bc3-0734-b3dac26193e4 at redhat dot com>
On Wed, 2016-06-15 at 09:09 +0200, Florian Weimer wrote:
> On 06/14/2016 08:21 PM, Torvald Riegel wrote:
> >> Maybe an explicit list of all modern glibc atomics somewhere would help
> >> to avoid all doubts.
> > I wouldn't like to maintain it on the wiki or such, but we could decide
> > to list the available atomics at the top of include/atomic.h, or
> > something like that. Would that have been helpful for you?
> Maybe extract the list using sed from the relevant header(s) and put it
> into the internals manual? If the naming convention is explained along
> the list, I don't think further per-macro documentation is necessary.
That's perhaps too much machinery or things we need to remember to do
for something that's rather simple to see by looking at
include/atomic.h, if one knows where to look for it.
I've updated https://sourceware.org/glibc/wiki/Concurrency with more
details on the naming scheme and instructions for how to easily see
which atomic operations we currently declare.