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,264
    • Issues 4,264
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 419
    • Merge Requests 419
  • 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
  • #3439

Closed
Open
Opened Aug 19, 2009 by Simon Peyton Jones@simonpjDeveloper

Improve the setup for ticky

Simon Marlow and I came up with the following proposals:

  • Merge the "ticky" and "debug" builds of the runtime system. This just simplifies the RTS build, and reduces the number of versions.
  • Arrange that every build of the RTS defines the symbols that are referenced by code compiled with -ticky. That way you won't get link errors if you compile tickified code with a non-debug RTS.

The second point is very important. When testing I often want to compile all the libraries with -ticky, but it's very fiddly to ensure that every program compiled against those libraries is linked against the debug/ticky RTS. I just want those programs to work. The ones I want to examine closely (ie see the ticky stats) I can certainly link with -ticky or -debug to get the RTS that does the counting.

None of this is difficult; just an hour or two's work.

Edited Mar 09, 2019 by Simon Peyton Jones
Assignee
Assign to
7.0.1
Milestone
7.0.1
Assign milestone
Time tracking
None
Due date
None
Reference: ghc/ghc#3439