[turbofan] --turbo should not imply --turbo-type-feedback.
authorBenedikt Meurer <bmeurer@chromium.org>
Thu, 21 May 2015 09:42:03 +0000 (11:42 +0200)
committerBenedikt Meurer <bmeurer@chromium.org>
Thu, 21 May 2015 09:41:55 +0000 (09:41 +0000)
The --turbo flag should reflect our TurboFan staging configuration, and
for now that does not include the JSTypeFeedbackSpecializer.

R=mstarzinger@chromium.org

Review URL: https://codereview.chromium.org/1150923005

Cr-Commit-Position: refs/heads/master@{#28535}

src/flag-definitions.h

index fad1139540c7409b9d312003ba48fe23fc701d30..f7cfffd026da6242e5825490b5807fbe0e0c8e38 100644 (file)
@@ -385,7 +385,6 @@ DEFINE_BOOL(omit_map_checks_for_leaf_maps, true,
 DEFINE_BOOL(turbo, false, "enable TurboFan compiler")
 DEFINE_BOOL(turbo_greedy_regalloc, false, "use the greedy register allocator")
 DEFINE_IMPLICATION(turbo, turbo_deoptimization)
-DEFINE_IMPLICATION(turbo, turbo_type_feedback)
 DEFINE_STRING(turbo_filter, "~~", "optimization filter for TurboFan compiler")
 DEFINE_BOOL(trace_turbo, false, "trace generated TurboFan IR")
 DEFINE_BOOL(trace_turbo_graph, false, "trace generated TurboFan graphs")