To: Scott Dillard
| Cc: Simon Peyton-Jones; Don Stewart; glasgow-haskell-users@haskell.org
| Subject: Re: laziness, memoization and inlining
|
| Scott Dillard wrote:
| > Simon, Don,
| >
| > You're right. -fno-state-hack fixed it. I've opened a trac ticket.
| > Program and t
Scott Dillard wrote:
Simon, Don,
You're right. -fno-state-hack fixed it. I've opened a trac ticket.
Program and test data are there.
http://hackage.haskell.org/trac/ghc/ticket/2284
Ok, but do we really need two tickets for this? Why open a new ticket
rather than adding the information to th
Simon, Don,
You're right. -fno-state-hack fixed it. I've opened a trac ticket.
Program and test data are there.
http://hackage.haskell.org/trac/ghc/ticket/2284
Scott
On Wed, May 14, 2008 at 1:48 AM, Simon Peyton-Jones
<[EMAIL PROTECTED]> wrote:
> Scott
>
> | I'm experiencing some undesirable
Scott
| I'm experiencing some undesirable performance behavior, I suspect from
| inlining things that shouldn't be, defeating my memoization attempts.
This is bad, very bad. I think Don is right. I believe the following is
happening. In your main program you have
do let mesh = memoMesh r
sedillard:
> Hi Everybody,
>
> I'm experiencing some undesirable performance behavior, I suspect from
> inlining things that shouldn't be, defeating my memoization attempts.
> I've been experimenting with purely functional 3D modeling code, so a
> mesh is (initially) something like
>
> > type Mes
