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

Remove --always-use-string-forwarding-table from --future

Browse Source 
Bug: chromium:1336516
Change-Id: I28a2b9d72e00a17792f80cf2a65312eeb47f165a
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3707290
Commit-Queue: Igor Sheludko <ishell@chromium.org>
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Auto-Submit: Patrick Thier <pthier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#81223}
This commit is contained in:
Patrick Thier 2022-06-17 14:40:04 +00:00 committed by V8 LUCI CQ
parent d500b7b853
commit ca29b0d3f6
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -747,10 +747,6 @@ DEFINE_BOOL(
// (enabled by --shared-string-table) are not supported using a single shared
// forwarding table.
DEFINE_NEG_IMPLICATION(shared_string_table, always_use_string_forwarding_table)
// TOOD(pthier): The code behind this flag is not going to ship.
// We enable it behind --future to get performance numbers and coverage from
// bots.
DEFINE_WEAK_IMPLICATION(future, always_use_string_forwarding_table)
DEFINE_BOOL(write_code_using_rwx, true,
"flip permissions to rwx to write page instead of rw")