Re: Re: [PATCHES] s_lock.h cleanup

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: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [PATCHES] s_lock.h cleanup
Date: 2001-01-19 18:42:37
Message-ID: 200101191842.NAA03543@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I believe the formatting problem was that some code had
> > "command;command; : lkjasfd : asldfk" while some had them spread over
> > separate lines, and others used \n\, all very randomly. Now at least
> > they are all consistent and use similar formatting.
>
> And they may all be broken, except for the one(s) you have tested.
> You shouldn't be assuming that a platform that uses gcc necessarily
> also uses gas.
>
> regards, tom lane

I can tell you that they all used __asm__, and all used the colon
terminators for each __asm__ block:

* __asm__ __volatile__(
* "command;"
* "command;"
* "command;"
* : "=r"(_res) return value, in register
* : "r"(lock) argument, 'lock pointer', in register
* : "r0"); inline code uses this register

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-19 18:43:22 Re: Re: Problems with BLOBs under Windows?
Previous Message Bruce Momjian 2001-01-19 18:40:16 Re: Re: [PATCHES] s_lock.h cleanup

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-01-19 18:49:26 Re: Re: [PATCHES] s_lock.h cleanup
Previous Message Bruce Momjian 2001-01-19 18:40:16 Re: Re: [PATCHES] s_lock.h cleanup