I'm debugging some code here where I get problems related to
spinlocks, anyhow, while running through the files I noticed
that the UNLOCK code seems sort of broken.
What I mean is that on machines that have loosely ordered
memory models you can have problems because of data that's
supposed to be
Alfred Perlstein [EMAIL PROTECTED] writes:
I'm pretty sure you guys need memory barrier ops.
On a machine that requires such a thing, the assembly code for UNLOCK
should include it. Want to provide a patch?
regards, tom lane
* Tom Lane [EMAIL PROTECTED] [001205 07:24] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
I'm pretty sure you guys need memory barrier ops.
On a machine that requires such a thing, the assembly code for UNLOCK
should include it. Want to provide a patch?
My assembler is extremely
