Re: solaris build problem with Sun compilers

Bruce Momjian wrote:
> 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".

Oh, I just found this email that has a simplified sparc8 asm:

http://archives.postgresql.org/pgsql-ports/2006-05/msg00025.php

Attached is the new solaris_sparc.s file with the #ifdef sparc8 test;
applied.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

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