pgsql: Replace ia64 S_UNLOCK compiler barrier with a full memory barrie

Поиск
Список
Период
Сортировка
От Andres Freund
Тема pgsql: Replace ia64 S_UNLOCK compiler barrier with a full memory barrie
Дата
Msg-id E1Z9YZb-0005iK-K3@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Дерево обсуждения 
Replace ia64 S_UNLOCK compiler barrier with a full memory barrier.

_Asm_sched_fence() is just a compiler barrier, not a memory barrier. But
spinlock release on IA64 needs, at the very least, release
semantics. Use a full barrier instead.

This might be the cause for the occasional failures on buildfarm member
anole.

Discussion: 20150629101108.GB17640@alap3.anarazel.de

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/07cb8b02ab4c8b65bb2e3b87ad2402fdc6cce978

Modified Files
--------------
src/include/storage/s_lock.h |    2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

В списке pgsql-committers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: pgsql: Fix the fallback memory barrier implementation to be reentrant.
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: pgsql: Run the C portions of guc-file.l through pgindent.