Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb]
| От | Noah Misch |
|---|---|
| Тема | Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb] |
| Дата | |
| Msg-id | 20111219200341.GB9495@tornado.leadboat.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb] (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb]
Re: [PATCH] Use CC atomic builtins if available [was: Re: TAS patch for building on armel/armhf thumb] |
| Список | pgsql-bugs |
On Mon, Dec 19, 2011 at 05:09:11PM +0200, Heikki Linnakangas wrote: > Actually, I believe our Itanium (and possibly ARM, too) implementation > of S_UNLOCK() is wrong as it is. There is no platform-specific > S_UNLOCK() defined for Itanium, so we're using the generic > implementation: > > #if !defined(S_UNLOCK) > #define S_UNLOCK(lock) (*((volatile slock_t *) (lock)) = 0) > #endif /* S_UNLOCK */ > > That is not sufficient on platforms with a weak memory model, like Itanium. Other processors may observe the lock as held after its release, but there's no correctness problem.
В списке pgsql-bugs по дате отправления: