S_LOCK() change produces error...

Поиск
Список
Период
Сортировка
От The Hermit Hacker
Тема S_LOCK() change produces error...
Дата
Msg-id Pine.NEB.3.96.980117213702.259C-100000@thelab.hub.org
обсуждение исходный текст
Ответы Re: [HACKERS] S_LOCK() change produces error...  (Bruce Momjian <maillist@candle.pha.pa.us>)
Список pgsql-hackers
I installed some patches today for the univel port, and one of the changes
did the following to include/storage/s_lock.h:

302c318
<                               __asm__("xchgb %0,%1": "=q"(_res), "=m"(*lock):"0"(0x1)); \
---
>                               __asm__("lock xchgb %0,%1": "=q"(_res), "=m"(*lock):"0"(0x1)); \


Under FreeBSD, this breaks the compile with an 'unimplemented' error...I'm
not going to commit the "fix" yet (reverse the patch)...does this break other
ports as well, or just FreeBSD?  Anyone with Assembler experience out there? :)


Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


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

Предыдущее
От: darrenk@insightdist.com (Darren King)
Дата:
Сообщение: Re: [HACKERS] Re: [QUESTIONS] Business cases
Следующее
От: The Hermit Hacker
Дата:
Сообщение: free() error in current source tree under FreeBSD...