Re: [HACKERS] Solaris ASM problem

2006-04-29 Thread Bruce Momjian
Theo Schlossnagle wrote: Kris Jurka wrote: On Fri, 28 Apr 2006, Theo Schlossnagle wrote: Kris Jurka wrote: Anyway the test exits with Stuck spinlock (80618e9) detected at ./s_lock.c:355. on a linux gcc build this exits with Stuck spinlock (0x5013ad) detected at

Re: [HACKERS] Solaris ASM problem

2006-04-29 Thread Theo Schlossnagle
Bruce Momjian wrote: Kris Jurka wrote: Bruce Momjian wrote: Log Message: --- Modify Solaris compiler build rules to use the cpp preprocessor, the the x86 file. Well it compiles now, but it doesn't seem to work:

Re: [HACKERS] Solaris ASM problem

2006-04-29 Thread Theo Schlossnagle
Kris Jurka wrote: On Fri, 28 Apr 2006, Theo Schlossnagle wrote: The file that uses the spinlocks: /src/backend/storage/lmgr/s_lock.c can be compiled standalone with -DS_LOCK_TEST To get the test to compile I had to link in tas.o as the attached patch shows. Unfortunately this doesn't

Re: [HACKERS] Solaris ASM problem

2006-04-29 Thread Theo Schlossnagle
Kris Jurka wrote: On Fri, 28 Apr 2006, Theo Schlossnagle wrote: What platform is that? (OS rev, architecture and word size)? I tested the changes I submitted on Solaris 10 amd64. $ uname -a SunOS albert 5.9 Generic_112234-03 i86pc i386 i86pc $ cc -V cc: Sun WorkShop 6 update 2 C 5.3

Re: [HACKERS] Solaris ASM problem

2006-04-29 Thread Theo Schlossnagle
Kris Jurka wrote: On Fri, 28 Apr 2006, Theo Schlossnagle wrote: Kris Jurka wrote: Anyway the test exits with Stuck spinlock (80618e9) detected at ./s_lock.c:355. on a linux gcc build this exits with Stuck spinlock (0x5013ad) detected at ./s_lock.c:402. This seems like a different

[HACKERS] Solaris ASM problem

2006-04-28 Thread Bruce Momjian
Kris Jurka wrote: Bruce Momjian wrote: Log Message: --- Modify Solaris compiler build rules to use the cpp preprocessor, the the x86 file. Well it compiles now, but it doesn't seem to work: http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=kududt=2006-04-28%2016:30:01

Re: [HACKERS] Solaris ASM problem

2006-04-28 Thread Kris Jurka
On Fri, 28 Apr 2006, Theo Schlossnagle wrote: What platform is that? (OS rev, architecture and word size)? I tested the changes I submitted on Solaris 10 amd64. $ uname -a SunOS albert 5.9 Generic_112234-03 i86pc i386 i86pc $ cc -V cc: Sun WorkShop 6 update 2 C 5.3 Patch 111680-09

Re: [HACKERS] Solaris ASM problem

2006-04-28 Thread Kris Jurka
On Fri, 28 Apr 2006, Theo Schlossnagle wrote: The file that uses the spinlocks: /src/backend/storage/lmgr/s_lock.c can be compiled standalone with -DS_LOCK_TEST To get the test to compile I had to link in tas.o as the attached patch shows. Unfortunately this doesn't work for platforms

Re: [HACKERS] Solaris ASM problem

2006-04-28 Thread Kris Jurka
On Fri, 28 Apr 2006, Theo Schlossnagle wrote: Kris Jurka wrote: Anyway the test exits with Stuck spinlock (80618e9) detected at ./s_lock.c:355. on a linux gcc build this exits with Stuck spinlock (0x5013ad) detected at ./s_lock.c:402. This seems like a different problem, no? The patch I