Remove now-unneeded check for GCC CAS from extconf.rb
CAtomic#get, #set, #swap have 'volatile' semantics

This patch ensures that a value #set on a CAtomic on one thread will
immediately be visible through #get on another thread. The intention is
that Atomic#get and #set should provide semantics like a Java 'volatile'
variable. The whole point of storing a value in an Atomic is because it will
be shared and modified from multiple threads, so it seems wrong that #get
and #set provide no particular memory-visibility guarantees. This
patch fixes that problem.

It would be better to use a load barrier for #get and a store barrier
for #set, but I don't know how to do that in a portable way. If maximum
performance is desired, it might be necessary to use inline assembly,
with #ifs based on the processor architecture.

The other variants of Atomic should be patched to provide the same
guarantees. The documentation should also be amended.
Merge pull request #145 from alexdowad/volatile_semantics_for_atomic_get_set

Volatile semantics for atomic get set