Opened 12 years ago

Last modified 3 years ago

#2255 new bug

Improve SpecConstr for free variables

Reported by: simonpj Owned by:
Priority: normal Milestone:
Component: Compiler Version: 6.8.2
Keywords: SpecConstr Cc: nfrisby
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Runtime performance bug Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


This ticket records a suggestion for improving SpecConstr, so we don't lose it. The original SpecConstr transformation is described in "Call pattern specialisation for Haskell". Consider this program

   f x = let g y = x of { z:zs -> e1; [] -> e2 } ...
 x of
                z:zs -> if ... then g 3 else g 4
                []   -> ...

Here 'x' is free in 'g', but x's value is known at g's call sites. It's not enough just to know "x is a cons" inside g; we must also have access to z,zs. So perhaps the thing to do is to imagine lambda-lifting 'g' to become 'gl' thus:

  gl x y = x of { z:zs -> e1; [] -> e2 } ...

  f x = x of
                z:zs -> if ... then gl x 3 else gl x 4
                []   -> ...

Now the SpecConstr transformation will apply nicely. And it's arguably a bad shortcoming that currently the mere act of lambda lifting can affect how effective SpecConstr is.

Of course, we only want to lambda-lift wrt the parameters that'll be specialised, so this transformation probably wants to be done at the same time as the rest of SpecConstr. I don't have much idea of how hard that'd be, but it's a nice idea.

Change History (5)

comment:1 Changed 11 years ago by simonmar

Architecture: UnknownUnknown/Multiple

comment:2 Changed 11 years ago by simonmar

Operating System: UnknownUnknown/Multiple

comment:3 Changed 10 years ago by simonmar

Type of failure: Runtime performance bug

comment:4 Changed 7 years ago by nfrisby

Cc: nfrisby added

comment:5 Changed 3 years ago by simonpj

Keywords: SpecConstr added
Note: See TracTickets for help on using tickets.