| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[test] Check output on the worker process. I added additional exception logging in the execution.py since errors in processing results were really difficult to debug. There is a problem on Windows with class serialization when it comes from dynamically loaded module. To fix it I moved all output processors to the tools/testrunner/outproc/ and import them in test/*/testcfg.py. Bug: v8:6917 Change-Id: Ida604641d659b006e91faf1d56a37769ec47f5f3 Reviewed-on: https://chromium-review.googlesource.com/842784 Commit-Queue: Michał Majewski <majeski@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50361} | 8 年前 | |
[turboshaft] Add --turboshaft-verify-load-elimination to numfuzz Be more forgiving for flags not existing in a configuration (e.g. a debug flag in release) when comparing expected output in webkit or message tests. The --turboshaft-verify-load-elimination only exists in debug and prints a warning in release. Bug: 404257893 Change-Id: Iff39d99845d25bacb68f82834a7d3dcc534d65ff Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6732621 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Darius Mercadier <dmercadier@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#101409} | 11 个月前 | |
[turboshaft][wasm] Add type assertions to type optimizer These assertions could help fuzzers in detecting type confusions in generated wasm-gc code. Bug: 450246010 Change-Id: I685b5b1a1d406459aeac4e1877e823e279ef2512 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7022989 Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#103045} | 8 个月前 | |
[wasm][fuzzer] Return -1 for non-interesting inputs This guides corpus generation in libfuzzer. Return -1 for any inputs which should not be added to the corpus. We also return -1 for cases which are still somewhat interesting (any invalid modules also has a chance to hit a decoder bug). We don't want those cases in the corpus though, as it's hard enough to generate valid modules for fuzzers. We will get enough invalid modules via random mutations. R=machenbach@chromium.org, mliedtke@chromium.org Bug: 384781857 Change-Id: I7c8833c45cb1dc8151bacb130906352c65f7511d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6180311 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#98654} | 1 年前 | |
[wasm] Introduce max deopts per function limit after which the optimizing compiler will not emit any deoptimization points for the function in question and fall back to emitting a non-inlined (indirect) call as slow path instead. Bug: 42204618 Change-Id: Ie5a41301d8fae9f0e380ff62a0ec380735672f2e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6281350 Reviewed-by: Daniel Lehmann <dlehmann@chromium.org> Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#98802} | 1 年前 | |
Remove v8heapconst.py from the repo .. and instead have the user regenerate it as needed (i.e. when using grokdump.py). v8heapconst.py has been a low-level-but-constant annoyance over the years. Changes to the known heap layout require manual regeneration, and if this happens on two active CLs at once, one of the two will 1) have a merge conflict, 2) require local v8heapconst.py regeneration, and finally 3) a re-upload and rerun of the entire CQ. The benefits of a prebuilt v8heapconst.py don't justify all this. This CL removes v8heapconst.py from the repo and adds regeneration instructions to the appropriate places. The test was updated to sanity-check generated output. Changes for users: running grokdump.py now requires rebuilding v8heapconst.py through gm.py mkdrokdump first. Change-Id: I7f371502ff6e5b287ec695d305abe0ae311a7e74 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4678628 Commit-Queue: Jakob Linke <jgruber@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#88878} | 2 年前 | |
[test] Check output on the worker process. I added additional exception logging in the execution.py since errors in processing results were really difficult to debug. There is a problem on Windows with class serialization when it comes from dynamically loaded module. To fix it I moved all output processors to the tools/testrunner/outproc/ and import them in test/*/testcfg.py. Bug: v8:6917 Change-Id: Ida604641d659b006e91faf1d56a37769ec47f5f3 Reviewed-on: https://chromium-review.googlesource.com/842784 Commit-Queue: Michał Majewski <majeski@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50361} | 8 年前 | |
[test262] Make async tests fail if $DONE() isn't called Bug: v8:14276 Change-Id: I0a2a1d71c23eff0811dc16eebfcbe7289f9ccbc2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4790965 Commit-Queue: Andreu Botella <abotella@igalia.com> Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#89600} | 2 年前 | |
[numfuzz] Gracefully ignore contradictory flags NumFuzz passes various flags to V8 testing randomly, which can lead to various flag contradictions with existing flags. Up to now the system ignored the check for contradictions and kept running the test cases, leading to false positives. This change adds a new v8 flag --exit-on-contradictory-flags that exists gracefully when a contradiction is detected. On the numfuzz side we now filter simple contradictions beforehand. Measurements showed that ~2% of all numfuzz tests ran into contradictions. Around half of them are simple contradictions (repetitions and inversions), which are now filtered beforehand. The remaining ones (redundant or contradictory implications) are now ignored. Bug: v8:11826 Change-Id: I9942e203ba9668a097fabe1343dd1365c9da94c1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3650746 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Almothana Athamneh <almuthanna@chromium.org> Cr-Commit-Position: refs/heads/main@{#80589} | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 8 年前 | ||
| 11 个月前 | ||
| 8 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 8 年前 | ||
| 2 年前 | ||
| 4 年前 |