Skip site navigation (1) Skip section navigation (2)

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

From: Martin Pitt <martin(at)piware(dot)de>
To: pgsql-ports(at)postgresql(dot)org, Roland Zippel <zippel(at)linux-m68k(dot)org>
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Date: 2004-06-13 08:22:52
Message-ID: 20040613082252.GA2754@donald.intranet.fbn-dd.de (view raw or flat)
Thread:
Lists: pgsql-ports
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(at)piware(dot)de                      mpitt(at)debian(dot)org
http://www.piware.de             http://www.debian.org

In response to

Responses

pgsql-ports by date

Next:From: Tom LaneDate: 2004-06-13 17:38:43
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'
Previous:From: Tom LaneDate: 2004-06-10 19:15:31
Subject: Re: Build failure on m68k and ia64: inconsistent operand constraints in an `asm'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group