Postgres Pro
Downloads
Home   >   mailing lists

Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm' - Mailing list pgsql-ports

From Martin Pitt
Subject Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Date
Msg-id 20040613082252.GA2754@donald.intranet.fbn-dd.de
Whole thread Raw
In response to Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-ports
Tree view 
Hi again!

On 2004-06-10 15:15 -0400, Tom Lane wrote:
> I think Debian broke their compiler and they ought to un-break it.

I asked Roland again, and got:

On 2004-06-11 10:10 +0200, Roman Zippel wrote:
> gcc developers disagree, we had same problem with the kernel, e.g. see:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107475162200773&w=2
>
> There is nothing broken with the compiler and changing the constraints of
> the memory operand to a "=m"/"m" pair is correctly understood by all
> versions of gcc.

Hmm. Since I cannot judge anyway, maybe you two can discuss that
directly and I implement whatever consensus you will reach?

Thanks and have a nice Sunday!

Martin

--
Martin Pitt                 Debian GNU/Linux Developer
martin@piware.de                      mpitt@debian.org
http://www.piware.de             http://www.debian.org
Attachment

pgsql-ports by date:

Previous
From: Tom Lane
Date:
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Next
From: Tom Lane
Date:
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'