I found myself frequently multiplying the mean duration by the number of calls to find the total time spent in a function. It is trivial to just have TimingScope show this information.
Created attachment 369317 [details] Patch trivial patch.
Comment on attachment 369317 [details] Patch Attachment 369317 [details] did not pass win-ews (win): Output: https://webkit-queues.webkit.org/results/12129493 New failing tests: http/tests/css/filters-on-iframes.html
Created attachment 369352 [details] Archive of layout-test-results from ews212 for win-future The attached test failures were seen while running run-webkit-tests on the win-ews. Bot: ews212 Port: win-future Platform: CYGWIN_NT-10.0-17763-3.0.5-338.x86_64-x86_64-64bit
Comment on attachment 369317 [details] Patch The windows bot appears red in general, it is not related to this patch.
Comment on attachment 369317 [details] Patch Clearing flags on attachment: 369317 Committed r245061: <https://trac.webkit.org/changeset/245061>
All reviewed patches have been landed. Closing bug.
<rdar://problem/50588584>