Commit 1ec34786 authored by Michael Achenbach's avatar Michael Achenbach Committed by Commit Bot

[foozzie] Don't whitelist GetOptimizationStatus for correctness fuzzing

This keeps it whitelisted for normal fuzzing.

TBR=neis@chromium.org

Bug: chromium:1070890, v8:10249
Change-Id: I9011db08741e1eef98672847809e7beb2abfe93b
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2154789Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#67238}
parent 8c685366
......@@ -201,7 +201,6 @@ bool Runtime::IsWhitelistedForFuzzing(FunctionId id) {
case Runtime::kDeoptimizeFunction:
case Runtime::kDeoptimizeNow:
case Runtime::kEnableCodeLoggingForTesting:
case Runtime::kGetOptimizationStatus:
case Runtime::kGetUndetectable:
case Runtime::kNeverOptimizeFunction:
case Runtime::kOptimizeFunctionOnNextCall:
......@@ -213,6 +212,7 @@ bool Runtime::IsWhitelistedForFuzzing(FunctionId id) {
// Runtime functions only permitted for non-differential fuzzers.
// This list may contain functions performing extra checks or returning
// different values in the context of different flags passed to V8.
case Runtime::kGetOptimizationStatus:
case Runtime::kHeapObjectVerify:
case Runtime::kIsBeingInterpreted:
return !FLAG_allow_natives_for_differential_fuzzing;
......
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