Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5,244
    • Issues 5,244
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 567
    • Merge requests 567
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell CompilerGlasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #16817
Closed
Open
Issue created Jun 13, 2019 by Ben Gamari@bgamari🐢Maintainer

Selectively reduce optimisation level in GHC build

Currently there are a few places in the GHC build where we do signficantly more time than is necessary or warranted, especially during development:

  • the stage0 ghc-cabal is built with $SRC_HC_OPTS, which contains -O in most build flavours. This means that we end up spending a significant amount of time compiling an optimized Cabal, despite the fact that stage0 ghc-cabal is hardly a performance critical executable.

  • stage2 Cabal is built with HsLibHcOpts, which contains -O in most build flavours. Not only is Cabal typically not going to be performance critical for users, but the object size from an unoptimised build is significantly smaller than that from an optimised build.

Edited Jan 23, 2020 by Ben Gamari
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking