From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | "Kevin P(dot) Neal" <kpneal(at)pobox(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Minimal patches for PostgreSQL 7.0b3 on NetBSD/alpha 1.4.1.... |
Date: | 2000-04-12 10:24:41 |
Message-ID: | Pine.GSO.4.02A.10004121219560.9188-100000@Myrslok.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 11 Apr 2000, Kevin P. Neal wrote:
> Here are minimal patches to get 7.0 beta 3 limping along on NetBSD/alpha
> release 1.4.1.
*** ./old/src/include/storage/s_lock.h Wed Jan 26 00:58:33 2000
--- ./new/src/include/storage/s_lock.h Sun Apr 9 23:56:46 2000
***************
*** 260,270 ****
--- 260,275 ----
#else /* i.e. not __osf__ */
#define TAS(lock) tas(lock)
#define S_UNLOCK(lock) { __asm__("mb"); *(lock) = 0; }
+ #if defined(__GNUC__)
+ static int /* GCC on the Alpha doesn't appear to handle
+ inlining of assembly with %0 or %1 properly.
*/
+ #else
static __inline__ int
+ #endif
tas(volatile slock_t *lock)
{
register slock_t _res;
__asm__(" ldq $0, %0 \n\
Any chance you could write a configure test that exposes this deficiency
rather than assuming that every GCC on every Alpha now and in the future
will have it? What does "doesn't appear to handle properly" mean anyway?
Have you notified the GCC maintainers?
Also, whose idea was it to use '__inline__' instead of 'inline'?
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-04-12 12:12:21 | Re: postgresql rule bug |
Previous Message | Mark Hollomon | 2000-04-12 07:45:48 | Re: Re: postgresql rule bug |