6546fcf180
Due to https://crbug.com/1195263, large typed arrays can have an observable difference on the same architecture, depending on optimization behavior. For differential fuzzing comparisons, we previously used a proxy for typed arrays that capped the maximum size only when comparing different architectures - there an observable difference is WAI. We move the capping code and make it arch-independent for now until the bug above gets fixed, since it caused too many duplicates, which degrade fuzzing performance. Bug: chromium:1195263 Change-Id: Ic81c383e547413378cbe037de3c38eb900a9e5dc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3866173 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#82860} |
||
|---|---|---|
| .. | ||
| codemap.mjs | ||
| compiler-trace-flags-wasm.js | ||
| compiler-trace-flags.js | ||
| consarray.mjs | ||
| csvparser.mjs | ||
| dumpcpp.mjs | ||
| foozzie_typed_arrays.js | ||
| foozzie_webassembly.js | ||
| foozzie.js | ||
| log_two_byte.js | ||
| log-ic.js | ||
| log.js | ||
| processor.mjs | ||
| profile_view.mjs | ||
| profile.mjs | ||
| splaytree.mjs | ||
| tickprocessor-test-func-info.log | ||
| tickprocessor-test-func-info.log.symbols.json | ||
| tickprocessor-test-large.default | ||
| tickprocessor-test-large.js | ||
| tickprocessor-test-large.log | ||
| tickprocessor-test-large.log.symbols.json | ||
| tickprocessor-test.default | ||
| tickprocessor-test.func-info | ||
| tickprocessor-test.gc-state | ||
| tickprocessor-test.ignore-unknown | ||
| tickprocessor-test.log | ||
| tickprocessor-test.log.symbols.json | ||
| tickprocessor-test.only-summary | ||
| tickprocessor-test.separate-bytecodes | ||
| tickprocessor-test.separate-ic | ||
| tickprocessor-test.separate-sparkplug-handlers | ||
| tickprocessor.mjs | ||
| timeline.mjs | ||