Clemens Hammacher 45618a9ab5 [wasm] Make prototype flags experimental ... Most prototype implementations are not fully supported in the interpreter. This is the case at least for exception handling, simd, and atomics. Any function can be redirected to the interpreter though, either by passing --wasm-interpret-all, or by dynamically redirecting to the interpreter for debugging. Making the flags experimental keeps the fuzzer from playing around with these flags. Drive-by: Refactor tests which explicitly set the prototype flag to use a new scope for that. R=ahaas@chromium.org BUG=chromium:727584 Change-Id: I67da79f579f1ac93c67189afef40c6524bdd4430 Reviewed-on: https://chromium-review.googlesource.com/519402 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#45639}		2017-05-31 14:18:08 +00:00
..
wasm	[wasm] Make prototype flags experimental	2017-05-31 14:18:08 +00:00
DEPS	[wasm] Move the wasm-module-runner from test/cctest to test/common	2016-09-14 10:31:53 +00:00