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

Re: solaris build problem with Sun compilers

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alan Stange <stange(at)rentec(dot)com>, pgsql-ports(at)postgresql(dot)org, Theo Schlossnagle <jesus(at)omniti(dot)com>
Subject: Re: solaris build problem with Sun compilers
Date: 2006-05-17 23:55:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-ports
Tom Lane wrote:
> Alan Stange <stange(at)rentec(dot)com> writes:
> > I believe the trick here is that Solaris 10 will only run on v9 hardware 
> > (or the sun4u systems), which all have the instruction.   But the v8 ABI 
> > "model" doesn't have it.   So, in some sense the ABI doesn't "allow" 
> > this instruction, but the hardware does, so they can just slam it in 
> > knowing that it'll work.
> Well, that might be OK for Sun's compiler since they know what a given
> version of Solaris will run on.  But I don't think we can adopt the same
> attitude for our gcc code path; that has to work on Sparc-based Linuxen
> and BSDen.  I don't think it's appropriate to kiss off support for v8
> chips when we haven't seen any proof at all of a performance boost in
> return.
> Maybe the right answer is to leave the code as-is, ie, deliberately not
> the same for Sun and gcc compilers.

OK, I have applied the following patch which documents that the Solaris
CC TAS ASM only works for sparc9.  Hopefully either sparc8 is not needed
(unlikely) or someone will fix it.  I have CC'ed the original
contributor who added "cas".

  Bruce Momjian

  + If your life is a hard drive, Christ can be your backup. +

Attachment: /bjm/diff
Description: text/x-diff (1.9 KB)

In response to


pgsql-ports by date

Next:From: Bruce MomjianDate: 2006-05-18 00:04:17
Subject: Re: solaris build problem with Sun compilers
Previous:From: Bruce MomjianDate: 2006-05-17 22:39:48
Subject: Re: solaris build problem with Sun compilers

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