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

Re: solaris build problem with Sun compilers

From: Alan Stange <stange(at)rentec(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-ports(at)postgresql(dot)org
Subject: Re: solaris build problem with Sun compilers
Date: 2006-05-12 21:11:59
Message-ID: 4464FA1F.6060805@rentec.com (view raw or flat)
Thread:
Lists: pgsql-ports
Tom Lane wrote:
> Alan Stange <stange(at)rentec(dot)com> writes:
>> This code isn't used by gcc, is it?  Or are you thinking to use the same 
>>   assembler segment in the inline function used by gcc?
> 
> The out-of-line .s files aren't used for gcc builds --- what's on the
> table here is whether to make the gcc inline assembler in s_lock.h
> match up with what's in the out-of-line files.
> 
>> Was there any reason given for the cas patch?
> 
> It appeared to me that the submitter just had a bee in his bonnet about
> cas being nicer ;-).  There might be something real to it, but AFAIR he
> didn't present any hard evidence.

Here's one workaround.

Check out the comment and implementation for cas32() in this .il 
template file for libc from OpenSolaris:

http://cvs.opensolaris.org/source/xref/on/usr/src/lib/libc/sparc/threads/sparc.il

In response to

Responses

pgsql-ports by date

Next:From: Tom LaneDate: 2006-05-12 21:33:04
Subject: Re: solaris build problem with Sun compilers
Previous:From: Tom LaneDate: 2006-05-12 20:44:04
Subject: Re: solaris build problem with Sun compilers

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