3 commits

Author	SHA1	Message	Date
Chris Wilson	6e0151df46	[cairo-atomic] Rearrange code under the correct ifdefs. ... The atomic get/set depend upon NEED_MEMORY_BARRIER which is separate from HAVE_ATOMIC_OPS.	2007-11-01 22:26:06 +00:00
Chris Wilson	71120727e1	[cairo-atomic] Use an atomic operation to set the status on a shared resource. ... Since the objects can be shared and may be in use simultaneously across multiple threads, setting the status needs to be atomic. We use a locked compare and exchange in order to avoid overwriting an existing error - that is we use an atomic operation that only sets the new status value if the current value is CAIRO_STATUS_SUCCESS.	2007-10-04 11:26:44 +01:00
Chris Wilson	8b6c871c90	[cairo-atomic] Introduce atomic ops. ... Test for the availability of the Intel __sync_* atomic primitives and use them to define a few operations useful for reference counting - providing a generic interface that may be targeted at more architectures in the future. If no atomic primitives are available, use a mutex based variant. If the contention on that mutex is too high, we can consider using an array of mutexes using the address of the atomic variable as the hash.	2007-09-25 16:29:54 +01:00