Bruce Momjian <pgman@candle.pha.pa.us> writes:
> If you are sure your storage and memory are good, I can think of only
> two other ideas. One is a gcc bug. You are running Itanium so it is
> possible. The only other possibility I can think of is that that our
> ia64 assembler code is wrong. It is:
But that code is gcc-only, and he's not using gcc.
It's certainly possible that the non-gcc spinlock path is broken on IA64
though. I dunno that anyone has ever tested that combination. It might
be interesting for him to run the "test" program in s_lock.c and see if
it complains.
regards, tom lane