Jakob Gruber 8c33e289b5 [coverage] Enable optimizations in block coverage modes ... Now that function counts are based on dedicated call counters instead of FeedbackVector::invocation_count, we can enable optimizations for block coverage modes. This significantly speeds up V8 with enabled coverage: Before this CL, the web-tooling-benchmark regressed by 70% (block count coverage vs. no coverage). With this CL, the regression is reduced to 40%. Bug: v8:6000,v8:9148 Change-Id: I6bb538bd66f32f016c66c1d1996bce3b25958232 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1615241 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61582}		2019-05-16 14:39:19 +00:00
..
console-profile-end-parameterless-crash-expected.txt
console-profile-end-parameterless-crash.js
console-profile-expected.txt
console-profile-wasm-expected.txt	Reland "[inspector] Add wasm profiling test"	2019-02-20 12:35:53 +00:00
console-profile-wasm.js	Reland "[inspector] Add wasm profiling test"	2019-02-20 12:35:53 +00:00
console-profile.js
coverage-block-expected.txt	[coverage] Enable optimizations in block coverage modes	2019-05-16 14:39:19 +00:00
coverage-block.js	[Test] Add --stress-flush-bytecode to gc-stress tester.	2018-12-13 18:37:56 +00:00
coverage-expected.txt	[parser] Force func decl allocation for non-block code coverage	2019-02-15 11:49:26 +00:00
coverage.js	[Test] Add --stress-flush-bytecode to gc-stress tester.	2018-12-13 18:37:56 +00:00
enable-disable-expected.txt
enable-disable.js
record-cpu-profile-expected.txt
record-cpu-profile.js
stop-without-preceeding-start-expected.txt
stop-without-preceeding-start.js