Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Дата
Msg-id 19582.1086842227@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Build failure on m68k and ia64: inconsistent operand constraints in an `asm'  (Martin Pitt <martin@piware.de>)
Ответы Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Список pgsql-ports
Martin Pitt <martin@piware.de> writes:
> Recently PostgreSQL did not build any more on the Debian ia64 and m68k buil=
> dds:

Just to clarify --- what you're reporting is that Debian changed their
compiler to break our code, right?  Because this asm has been the same
for quite awhile ...

> A Debian porter suggested that "1"(*lock) is an obsolete syntax and
> should be replaced by "m"(*lock) in both cases; however, I would like
> to get a second opinion about this.

We will need to find out whether this syntax also works with older
gccs, and if not, what hoops we must leap through to determine which
syntax to use.

            regards, tom lane

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

Предыдущее
От: Martin Pitt
Дата:
Сообщение: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Следующее
От: Martin Pitt
Дата:
Сообщение: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'