[m-rev.] for review: deconstruct.named_arg for java

[Paul Bone]

On Wed, Jul 14, 2010 at 03:48:27PM +1000, Ian MacLarty wrote:
> On Wed, Jul 14, 2010 at 3:15 PM, Zoltan Somogyi <zs at csse.unimelb.edu.au> wrote:
> > On 14-Jul-2010, Ian MacLarty <maclarty at csse.unimelb.edu.au> wrote:
> >> That doesn't appear to solve the problem.  The function is actually
> >> used.  What is needed is a "defined" attribute to convince gcc that
> >> the function is actually defined.
> >
> > Since the state of things as they were before all this started actually
> > worked, I think gcc was sufficiently convinced already.
> >
> 
> I'm not sure what you mean.  As far as I know gcc 4.x has always
> emitted these warnings for the code generated in asm_fast.gc.
> 

I remember this problem occuring back in 2007 when I first compiled Mercury at
home.

Zoltan may not have seen it before since his workstation had been configured to
use gcc-3.4.  taura is one of the last systems to be switched to gcc 4.x for
Mercury's nightly builds.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20100714/9931e567/attachment.sig>