• Clemens Backes's avatar
    [wasm][fuzzer] Fix BigInt parameters · 2d78b3a7
    Clemens Backes authored
    The fuzzers were calling the compiled function without passing explicit
    arguments. Thus all arguments were converted from the "undefined" value,
    which typically results in a zero value, as expected.
    For BigInt though, it's not allowed to pass "undefined". We have to pass
    a proper BigInt.
    This CL implements this by passing explicit parameter values for all
    parameters.
    
    This effectively unlocks testing BigInt parameters in all fuzzers, thus
    may increase coverage and find new bugs.
    
    R=ahaas@chromium.org
    
    Bug: chromium:1120355
    Change-Id: I4e451d2418eb73d460fa937d1cf95a1ab6c99cf5
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2377945
    Commit-Queue: Clemens Backes <clemensb@chromium.org>
    Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#69570}
    2d78b3a7
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
fuzzilli Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...