#9419: Machine-readable output for profiling -------------------------------------+------------------------------------- Reporter: ezyang | Owner: ezyang Type: feature request | Status: new Priority: normal | Milestone: Component: Profiling | Version: 7.9 Keywords: | Operating System: Architecture: Unknown/Multiple | Unknown/Multiple Difficulty: Unknown | Type of failure: Blocked By: | None/Unknown Related Tickets: | Test Case: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- We'll control whether or not machine-readable output is used using the `--machine-readable` flag currently used for GC stats. The format should also be self-explanatory for cost-center stats: per cost center we output the a CSV of `cc->time_ticks`, `cc->mem_alloc`. I'm a little less sure how to format the hierarchical cost center stacks; we could print out the entire trace of the stack, or maybe even organize the data recursively from the get go (outputting something JSON like, in that case.) -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/9419 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler