f774d8c56f
Once we enabled --turbo by default we need to turn all the implications off with --no-turbo as well. Chrome sets flags in V8 using SetFlagFromString, which enforces the implications each time it is called. Therefore, if --turbo is enabled by default, and an unrelated flag is set, the turbo implications are enabled but not later disabled if we set --no-turbo. To fix this, add negative implications as well. BUG=chromium:692409 Change-Id: Iadb0ca542f49ba65c7419cda8c7a03636a8d5ba9 Reviewed-on: https://chromium-review.googlesource.com/451320 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#43655} |
||
---|---|---|
.. | ||
dead-code-source-position.js | ||
ignition-statistics-extension.js | ||
optimized-stack-trace.js | ||
osr-from-bytecode.js | ||
osr-from-generator.js | ||
regress-5768.js | ||
regress-597565-double-to-object-transition.js | ||
regress-599001-verifyheap.js | ||
regress-612386-smi-to-double-transition.js | ||
regress-616064.js | ||
regress-629792-source-position-on-jump.js | ||
regress-662418.js | ||
regress-664146.js | ||
regress-672027.js | ||
stack-trace-source-position.js | ||
tracing.js |