This option would provide more detail than the reportXXXCompileTimes options. It would show the times for each phase of DFG / FTL compilation.
Created attachment 291981 [details] Patch
Comment on attachment 291981 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=291981&action=review > Source/JavaScriptCore/dfg/DFGPhase.h:82 > + before = monotonicallyIncreasingTimeMS(); Given that the DFG can run on a separate JIT thread concurrently, should you be using currentCPUTime() instead?
Comment on attachment 291981 [details] Patch r=me
(In reply to comment #2) > Comment on attachment 291981 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=291981&action=review > > > Source/JavaScriptCore/dfg/DFGPhase.h:82 > > + before = monotonicallyIncreasingTimeMS(); > > Given that the DFG can run on a separate JIT thread concurrently, should you > be using currentCPUTime() instead? All of the other time stats for the compiler tiers use monotonicallyIncreasingTime(). Given that the compilation threads "should" run without being preempted, I think we're fine.
Comment on attachment 291981 [details] Patch Clearing flags on attachment: 291981 Committed r207491: <http://trac.webkit.org/changeset/207491>
All reviewed patches have been landed. Closing bug.