Commit 99d1e5dc authored by mstarzinger's avatar mstarzinger Committed by Commit bot

[turbofan] Remove obsolete --turbo-shipping flag.

By now TurboFan is shipping on a broad range of language constructs and
wholesale disabling TurboFan can still be done with the --turbo-filter
flag. A dedicated flag controlling AST numbering heuristics is no longer
needed.

R=bmeurer@chromium.org

Review-Url: https://codereview.chromium.org/2155243006
Cr-Commit-Position: refs/heads/master@{#37900}
parent 52a66bf1
......@@ -56,12 +56,7 @@ class AstNumberingVisitor final : public AstVisitor<AstNumberingVisitor> {
DisableSelfOptimization();
}
void DisableCrankshaft(BailoutReason reason) {
if (FLAG_turbo_shipping) {
properties_.flags() |= AstProperties::kDontCrankshaft;
} else {
dont_optimize_reason_ = reason;
DisableSelfOptimization();
}
properties_.flags() |= AstProperties::kDontCrankshaft;
}
template <typename Node>
......
......@@ -425,7 +425,6 @@ DEFINE_BOOL(turbo, false, "enable TurboFan compiler")
DEFINE_IMPLICATION(turbo, turbo_asm_deoptimization)
DEFINE_IMPLICATION(turbo, turbo_store_elimination)
DEFINE_IMPLICATION(turbo, turbo_loop_peeling)
DEFINE_BOOL(turbo_shipping, true, "enable TurboFan compiler on subset")
DEFINE_BOOL(turbo_from_bytecode, false, "enable building graphs from bytecode")
DEFINE_BOOL(turbo_sp_frame_access, false,
"use stack pointer-relative access to frame wherever possible")
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment