Re: BUG #6331: Cross compile error/aborts. Works if '--disable-spinlock' is used

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: vbberdin(at)yahoo(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6331: Cross compile error/aborts. Works if '--disable-spinlock' is used
Date: 2011-12-13 01:09:55
Message-ID: 4EE6A5E3.6070400@ringerc.id.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 13/12/11 08:43, Tom Lane wrote:
> Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> writes:
>> because AFAIK there's no ARM asm code or ARM gcc intrinsics hidden away
>> in Pg, and that'd be the only other way to get those kinds of errors.
> No, you're mistaken about that: we do have inline assembly code in
> s_lock.h, and this message does look to be complaining about that code,
> because "swpb %0, %0, [%2]" is exactly what the TAS() macro generates
> for ARM.
Ah - my mistake, and thanks for the correction. I really should've seen
that.

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John Lumby 2011-12-13 14:18:05 Re: LIKE predicate and ERROR: 42P22: could not determine which collation to use for string comparison - HINT: Use the COLLATE clause ...
Previous Message Tom Lane 2011-12-13 00:43:06 Re: BUG #6331: Cross compile error/aborts. Works if '--disable-spinlock' is used