Re: Spinlocks and compiler/memory barriers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Spinlocks and compiler/memory barriers
Date: 2014-08-05 15:55:18
Message-ID: CA+TgmobeR9fNUqtafFypBNvg56kpkJQW3CExxYdv6N-2wsO6fA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 6, 2014 at 3:12 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> > If you want to do that, it's fine with me. What I would do is:
>> >
>> > - Back-patch the addition of the sparcv8+ stuff all the way. If
>> > anyone's running anything older, let them complain...
>> > - Remove the special case for MIPS without gcc intrinsics only in
>> > master, leaving the back-branches broken. If anyone cares, let them
>> > complain...
>> > - Nothing else.
>>
>> I've gone ahead and done the second of these things.
>
> Thanks.
>
>> Andres, do you want to go take a stab at fixing the SPARC stuff?
>
> Will do, will probably take me till thursday to come up with the brain
> cycles.

Ping?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-08-05 16:35:17 Re: Fixed redundant i18n strings in json
Previous Message Robert Haas 2014-08-05 15:51:51 Re: Scaling shared buffer eviction