3864e1f2da
This subsumes the old behavior of --allow-natives-for-fuzzing under --fuzzing as well. Both flags are used in a redundant way in fuzz configs. Only --allow-natives-for-fuzzing wasn't specified as a required argument, leading to the bug below. We still need the flag --allow-natives-for-differential-fuzzing to allow different functions when using differential fuzzing. Bug: chromium:1094866 Change-Id: I398791779e58ed4d80e896c1cfea343848159212 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2246568 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#68401}
27 lines
935 B
JavaScript
27 lines
935 B
JavaScript
// Copyright 2020 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Flags: --allow-natives-syntax --fuzzing
|
|
|
|
// Test whitelisted/blacklisted intrinsics in the context of fuzzing.
|
|
|
|
// Blacklisted intrinsics are replaced with undefined.
|
|
assertEquals(undefined, %ConstructConsString("a", "b"));
|
|
|
|
// Blacklisted intrinsics can have wrong arguments.
|
|
assertEquals(undefined, %ConstructConsString(1, 2, 3, 4));
|
|
|
|
// We don't care if an intrinsic actually exists.
|
|
assertEquals(undefined, %FooBar());
|
|
|
|
// Check whitelisted intrinsic.
|
|
assertNotEquals(undefined, %IsBeingInterpreted());
|
|
|
|
// Whitelisted runtime functions with too few args are ignored.
|
|
assertEquals(undefined, %DeoptimizeFunction());
|
|
|
|
// Superfluous arguments are ignored.
|
|
%DeoptimizeFunction(function() {}, undefined);
|
|
assertNotEquals(undefined, %IsBeingInterpreted(1, 2, 3));
|