2970249a72
The `compiler-trace-flags.js` test just makes sure the various --trace-turbo* flags do not cause V8 to crash. However, on builds with no snapshot, they would generate a *lot* of output as they were tracing the compiler while generating the snapshot. Let's set the `--trace-turbo-filter` flag to make sure we only trace the test functions. Sadly, WASM functions do not have a name, just an index, so we have to split this test into two. Bug: chromium:943064 Cq-Include-Trybots: luci.v8.try:v8_win_nosnap_shared_rel_ng Change-Id: I30b3935f63d412ab8c96cc5156d342c428229865 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532078 Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#60383} |
||
---|---|---|
.. | ||
codemap.js | ||
compiler-trace-flags-wasm.js | ||
compiler-trace-flags.js | ||
consarray.js | ||
csvparser.js | ||
dumpcpp.js | ||
profile_view.js | ||
profile.js | ||
profviz-test.default | ||
profviz-test.log | ||
profviz.js | ||
splaytree.js | ||
tickprocessor-test-func-info.log | ||
tickprocessor-test.default | ||
tickprocessor-test.func-info | ||
tickprocessor-test.gc-state | ||
tickprocessor-test.ignore-unknown | ||
tickprocessor-test.log | ||
tickprocessor-test.only-summary | ||
tickprocessor-test.separate-ic | ||
tickprocessor.js |