Re: Sun inline assembler ... - Mailing list pgsql-bugs

From Hans-Jürgen Schönig
Subject Re: Sun inline assembler ...
Date
Msg-id 42CD4856.5080501@cybertec.at
Whole thread Raw
In response to Re: Sun inline assembler ...  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Sun inline assembler ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I have seen that.
The question is: Gcc seems to get it right ;).
In my little world two compiler should handle this the same but I have
learned that Sun is in many cases different world ...
1+1 is always 2 - on Sun it could also be 3 ;).
hans



Michael Fuhr wrote:
> On Thu, Jul 07, 2005 at 04:53:16PM +0200, Hans-Jürgen Schönig wrote:
>
>>I have some minor troubles when using the Sun Compiler 9 on Solaris 9.
>>The spinlock assembler code is somehow broken for Solaris 9 and Solaris
>>10 (it works for Sun CC 8).
>>
>>The following patch fixes this:
>>
>>[hs@localhost postgresql-8.0.1]$ cd src/backend/storage/lmgr/
>>[hs@localhost lmgr]$ diff s_lock.c /tmp/fixed_s_lock.c
>>248,249c248,249
>><       asm(".section \"data\"");
>><       asm(".section \"text\"");
>>---
>>
>>>      asm(".seg \"data\"");
>>>      asm(".seg \"text\"");
>
>
> There's already an #ifdef around that code -- is it not matching
> correctly for your compiler?  Here's what I see in REL8_0_STABLE
> and in HEAD (s_lock.c 1.35):
>
> 244 #ifdef SUNOS4_CC
> 245     asm(".seg \"data\"");
> 246     asm(".seg \"text\"");
> 247 #else
> 248     asm(".section \"data\"");
> 249     asm(".section \"text\"");
> 250 #endif
>
> This looks like the thread that led to the above code:
>
> http://archives.postgresql.org/pgsql-patches/2004-12/msg00213.php
>



pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: BUG #1756: PQexec eats huge amounts of memory
Next
From: Tom Lane
Date:
Subject: Re: Sun inline assembler ...