Re: __sync barriers

2010-11-24 Thread Ken Werner
On Monday, November 22, 2010 12:34:04 pm Richard Sandiford wrote: > For the record, the thing I half-remembered on the call was: > > http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00697.html > and: > http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02112.html > > The problem is that all __sync

Re: __sync barriers

2010-11-22 Thread Michael Hope
On Tue, Nov 23, 2010 at 12:34 AM, Richard Sandiford wrote: > For the record, the thing I half-remembered on the call was: > >    http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00697.html > and: >    http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02112.html > > The problem is that all __sync operations

__sync barriers

2010-11-22 Thread Richard Sandiford
For the record, the thing I half-remembered on the call was: http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00697.html and: http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02112.html The problem is that all __sync operations besides __sync_lock_test_and_set and __sync_lock_release are defined