[constant-tracking] Track constants by default.
It is possible this CL results in various regressions, the idea is to get some data on where constant tracking helps and where it regresses. Bug: v8:8361 Change-Id: I2f291788a8bea03e6eaac9f51564c1da02734d1a Reviewed-on: https://chromium-review.googlesource.com/c/1347474 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#58008}
This commit is contained in:
parent
f3398adf55
commit
a6669bdce7
@ -975,9 +975,9 @@ DEFINE_BOOL(trace_ic, false,
|
||||
DEFINE_IMPLICATION(trace_ic, log_code)
|
||||
DEFINE_INT(ic_stats, 0, "inline cache state transitions statistics")
|
||||
DEFINE_VALUE_IMPLICATION(trace_ic, ic_stats, 1)
|
||||
DEFINE_BOOL_READONLY(track_constant_fields, false,
|
||||
DEFINE_BOOL_READONLY(track_constant_fields, true,
|
||||
"enable constant field tracking")
|
||||
DEFINE_BOOL_READONLY(modify_map_inplace, false, "enable in-place map updates")
|
||||
DEFINE_BOOL_READONLY(modify_map_inplace, true, "enable in-place map updates")
|
||||
DEFINE_BOOL_READONLY(fast_map_update, false,
|
||||
"enable fast map update by caching the migration target")
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user