This is the mail archive of the
mailing list for the glibc project.
Re: Consensus on MT-, AS- and AC-Safety docs.
- From: Rich Felker <dalias at aerifal dot cx>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Sun, 1 Dec 2013 13:08:37 -0500
- Subject: Re: Consensus on MT-, AS- and AC-Safety docs.
- Authentication-results: sourceware.org; auth=none
- References: <528A7C8F dot 8060805 at redhat dot com> <52991C3B dot 9080701 at redhat dot com> <ord2lhjnku dot fsf at livre dot home> <1385921165 dot 3152 dot 11533 dot camel at triegel dot csb>
On Sun, Dec 01, 2013 at 07:06:05PM +0100, Torvald Riegel wrote:
> > It
> > doesn't cover all of the richness of the atomics of recent C and C++
> > standards, but a basic memory model in which they can fit in perfectly
> > is there: concurrent writes or reads and writes to the same memory
> > location, without intervening synchronization operations, invoke
> > undefined behavior. This is the memory model that POSIX exposes to
> > users.
> That's not a complete definition, obviously. That's an attempt at
> describing the rough idea behind a memory model.
That is a memory model. It may not be the ideal memory model we want,
but it's a memory model because it defines the situations in which
memory accesses are well-defined and explicitly leaves the behavior
completely undefined in all other cases.