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,388
    • Issues 4,388
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 378
    • Merge Requests 378
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #19081

Closed
Open
Opened Dec 17, 2020 by Sebastian Graf@sgraf812Developer

Building a stage3 compiler as a(n optional?) compiler perf test in CI

I think a stage3 build would make for a marvellous ghc/alloc test case. We could compare the ghc/alloc metric between the stage1 (or the stage2 compiler of a previous an ancestor commit) and the stage2 compiler.

Although we'd have to be careful to build stage1 and stage2 with the same flags throughout. So probably better just compare to the stage2 metric of the ancestor commit.

It's also a pretty good way to assess whether a new optimisation should go in -O1 or -O2.

Maybe we could make one of the full-build jobs build the stage3 compiler?

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