AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

Disabe FLAG_turbo_control_flow_aware_allocation again

Browse Source 
A few changes have been made to this feature and disabling it lets us
best see its current performance impact.

Bug: v8:9088
Change-Id: I54d5e09f3fcece215e29d66d5bdb3f19ba07bda0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1690954
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#62586}
This commit is contained in:
Georg Neis 2019-07-08 15:23:26 +02:00 committed by Commit Bot
parent 2e54e9af61
commit a6eabacfee
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/flags/flag-definitions.h
View File

@ -464,7 +464,7 @@ DEFINE_BOOL(print_deopt_stress, false, "print number of possible deopt points")
DEFINE_BOOL(opt, true, "use adaptive optimizations")
DEFINE_BOOL(turbo_sp_frame_access, false,
"use stack pointer-relative access to frame wherever possible")
DEFINE_BOOL(turbo_control_flow_aware_allocation, true,
DEFINE_BOOL(turbo_control_flow_aware_allocation, false,
"consider control flow while allocating registers")
DEFINE_STRING(turbo_filter, "*", "optimization filter for TurboFan compiler")