[Flags] Add --enable-future-v8-vm-features to about:flags
This enables web developers, testers and Chromiumd developers to
try upcoming V8 VM features. It intentionally does not include
features that modify the JavaScript API. This is controlled via
a separate, already existing flag.
Bug: 772325
Change-Id: I1af202f1bfc5d21c73521a2066f690b0a44f870e
Reviewed-on: https://chromium-review.googlesource.com/704694
Commit-Queue: Michael Hablich <[email protected]>
Reviewed-by: Jochen Eisinger <[email protected]>
Cr-Commit-Position: refs/heads/master@{#510805}diff --git a/content/renderer/render_process_impl.cc b/content/renderer/render_process_impl.cc
index 892e61e..9056850 100644
--- a/content/renderer/render_process_impl.cc
+++ b/content/renderer/render_process_impl.cc
@@ -157,6 +157,9 @@
SetV8FlagIfNotFeature(features::kWebAssembly,
"--wasm-disable-structured-cloning");
+ SetV8FlagIfFeature(features::kV8VmFuture, "--future");
+ SetV8FlagIfNotFeature(features::kV8VmFuture, "--no-future");
+
SetV8FlagIfFeature(features::kWebAssemblyTrapHandler, "--wasm-trap-handler");
SetV8FlagIfNotFeature(features::kWebAssemblyTrapHandler,
"--no-wasm-trap-handler");
