Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
GHC
GHC
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,247
    • Issues 4,247
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 393
    • Merge Requests 393
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #18886

Closed
Open
Opened Oct 25, 2020 by Sebastian Graf@sgraf812Developer

DmdAnal: Speed up the first demand analysis run by not recording used-once information

I don't really see how we use used-once/single-entry information (e.g. the 1* part of demand signatures) after the first round of demand analysis. Well, maybe a bit for eta-expansion of thunks, not sure.

The used-once information is quite inefficient to compute compared to a plain strictness+absence analysis. I think we could parameterise demand analysis by analysis mode, which would allow us to avoid inefficient postProcess* calls and whatnot in all but the very last demand analysis run, where we actually exploit used-once information for identifying single-entry thunks.

If we see that we actually lose performance, we can still do the full analysis in -O2 and plain strictness+absence in -O1.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ghc/ghc#18886