Skip site navigation (1) Skip section navigation (2)

Re: GCC builtins for atomic-test-and-set, memory barries, and such

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GCC builtins for atomic-test-and-set, memory barries, and such
Date: 2007-09-24 03:42:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> When reading Tom's comment about the bug in my "use latestCompletedXid 
> to slightly speed up TransactionIdIsInProgress" patch, I remembered that 
> I recently stumbled across GCC builtins for atomic test-and-test and
> read/write reordering barriers...

> Has anyone looked into those? It seems that those could be used to 
> provide a fallback spinlock implementation - though maybe we already 
> cover all interesting targets, and it's not worth the effort.

It doesn't seem very interesting given that (a) we already have working
code for this area, and (b) gcc is not our only target compiler.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-09-24 03:52:55
Subject: pgsql: Reduce the size of memory allocations by lazy vacuum when
Previous:From: Andrew DunstanDate: 2007-09-24 02:44:51
Subject: Re: Problem with MSVC install script

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group