Simple machine-readable output for profiling, CC only.
Needs RevisionPublic

Authored by ezyang on Aug 7 2014, 8:28 AM.

Details

Reviewers
simonmar
hvr
austin
Trac Issues
#9419
Summary

ToDo: Documentation

ToDo: Figure out what to do with CCSes

ToDo: Bikeshed command line flags

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Test Plan

add a profiling test, validate

Diff Detail

Repository
rGHC Glasgow Haskell Compiler
Branch
ezyang-profiled
Lint
Lint ErrorsExcuse: unrelated code
SeverityLocationCodeMessage
Errorrts/Profiling.c:52TXT2Tab Literal
Unit
No Unit Test Coverage
Build Status
Buildable 334
Build 335: GHC Patch Validation (amd64/Linux)
ezyang updated this revision to Diff 280.Aug 7 2014, 8:28 AM
ezyang retitled this revision from to Simple machine-readable output for profiling, CC only..
ezyang edited the test plan for this revision. (Show Details)
ezyang added reviewers: simonmar, hvr, austin.
ezyang updated the Trac tickets for this revision.
ezyang updated this object.

Yay! Build B335: Diff 280 (D124) has succeeded! Full logs available at F11839.

simonmar edited edge metadata.Aug 11 2014, 2:27 AM

Doesn't seem very useful without CCSs. When you put "ToDo" in the description, does that mean you want to do those things before the diff is ready to commit, or you want to commit this and do them later?

The ToDo items are things that we should do before it goes in. The big problem with CCSes is I'm not really sure what a good format is for them. I tried to figure out what kind of output is easily understandable by tools like R, but came up empty.

simonmar requested changes to this revision.Oct 1 2014, 5:33 AM
simonmar edited edge metadata.

Back to your queue

This revision now requires changes to proceed.Oct 1 2014, 5:33 AM
austin resigned from this revision.Nov 6 2017, 4:02 PM