Ticket #19 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

SPEC interferes with optimisations

Reported by: rl Owned by:
Priority: critical Milestone: 0.7
Version: 0.6 Keywords:
Cc:

Description

Since SPEC is a sum type and we immediately inspect it in a loop, the demand analyser can't infer the strictness of the other loop arguments. Perhaps seq on it instead of pattern matching? Originally spotted while working on #18.

Change History

Changed 3 years ago by rl

  • priority changed from minor to major
  • milestone set to 0.7

Changed 3 years ago by rl

Of course, another possibility is to teach w/w about SPEC which would remove the need for a sum type.

Changed 3 years ago by rl

It turns out that inspecting SPEC also triggers LiberateCase. This is bad since it affects 6.13 as well. Just seq'ing would probably help here.

Changed 3 years ago by rl

  • summary changed from SPEC interferes with strictness analysis to SPEC interferes with optimisations

Changed 3 years ago by rl

  • priority changed from major to critical

Changed 3 years ago by rl

  • status changed from new to closed
  • resolution set to fixed

Mon May 24 14:43:00 EST 2010 Roman Leshchinskiy <rl@…>

  • Don't actually inspect SPEC, just seq on it
Note: See TracTickets for help on using tickets.