pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Emils Klotins <emils@grafton.lv>
Cc: pgsql-sql@hub.org
Subject: Re: Q: spinlock on Alpha? (PG7.0.2)
Date: Mon, 02 Oct 2000 02:36:27 -0400
Message-ID: <995.970468587@sss.pgh.pa.us> (raw)
In-Reply-To: <39D83B60.5071.11490464@localhost>
References: <39D83B60.5071.11490464@localhost>

"Emils Klotins" <emils@grafton.lv> writes:
> RedHat Linux 6.2 on Alphaserver DS10 (egcs-1.1.2, glibc-2.1.3, 
> libstdc++-2.9.0).
> Postgresql-7.0.2 source

> Compiles and installs just fine. However, both the regular initdb and 
> parallel regression testing's initdb stage fails with a core file and 
> message:

> FATAL: s_lock (2030d360) at spin.c:116, stuck spinlock. Aborting.
> FATAL: s_lock (2030d360) at spin.c:116, stuck spinlock. Aborting.

I was just fooling with PG on a RedHat Alpha box that DEC kindly
loaned to the project.  It looks like the above problem is caused
by compiler optimization; although src/template/linux_alpha
optimistically sets CFLAGS=-O2, I had to back off to -O1 to avoid
that same spinlock complaint, and I couldn't get 7.0.* to pass
regression tests with anything but -O0.  (And even there, there
were a bunch of failures in the datetime-related tests; it looks
like our abstime datatype breaks rather badly on this platform.)

I haven't had time yet to try current sources on that box, but
I'm optimistic that the new function manager will solve a lot of
portability problems on Alphas.  Still, I don't understand why -O2
breaks spinlocks --- maybe egcs is misoptimizing around the inline
assembly code of tas() ?

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <995.970468587@sss.pgh.pa.us>
Permalink:  ../995.970468587@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/995.970468587@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, emils@grafton.lv, pgsql-sql@hub.org
  Subject: Re: Q: spinlock on Alpha? (PG7.0.2)
  In-Reply-To: <995.970468587@sss.pgh.pa.us>
  References: <39D83B60.5071.11490464@localhost> <995.970468587@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox