This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: mutually-recursive types and an old puzzle

From: Zack Weinberg <zack at codesourcery dot com>
To: Joe Buck <Joe dot Buck at synopsys dot COM>
Cc: Gabriel Dos Reis <gdr at acm dot org>, Chris Lattner <sabre at nondot dot org>, gcc at gcc dot gnu dot org
Date: Wed, 30 Jun 2004 12:38:00 -0700
Subject: Re: mutually-recursive types and an old puzzle
References: <Pine.LNX.4.44.0406291930070.1537-100000@nondot.org><32877.::ffff:128.194.146.36.1088556186.squirrel@webmail.nerim.net><20040629175356.A11677@synopsys.com><32929.::ffff:128.194.146.36.1088557164.squirrel@webmail.nerim.net><20040630122238.A23557@synopsys.com>

Joe Buck <Joe.Buck@synopsys.COM> writes:

>> I just gave a hint to why the fixpoint operator of C++ may suffice
>> to solve the puzzle -- it wasn't an final solution.
>
> Here's one, if anyone's curious.  The class has one member, which is
> a function pointer; the operator() overload calls the function pointer.

This works, but doesn't get optimized down to ideal code, mainly
because the ABI prevents FsmState from being returned in a register
(since it's not a POD structure).

zw

References:
- RE: mutually-recursive types and an old puzzle
  - From: Chris Lattner
- Re: mutually-recursive types and an old puzzle
  - From: Joe Buck
- Re: mutually-recursive types and an old puzzle
  - From: Joe Buck

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]