Skip to content

GitLab

  • Menu
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 4,968
    • Issues 4,968
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 473
    • Merge requests 473
  • 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 Compiler
  • GHCGHC
  • Issues
  • #8272
Closed
Open
Created Sep 12, 2013 by Carter Schonwald@carterDeveloper

Consider using native stack pointer register for STG stack

There are a variety of reasons why we might want to use the native stack pointer register to track the STG stack:

  • Performance might be better for a variety of reasons:
    • we could possibly use PUSH instead of MOV on x86, which has a more succinct encoding
    • the LLVM backend would be able to make better assumptions about pointer aliasing(?)
    • microarchitecture implementations likely optimise for stack accesses
  • In conjunction with DWARF debug information we could more easily use perf and other performance measurement tools (e.g. #15929)
Edited Jun 24, 2019 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