Teach fuzzer about --noanalyze-environment-liveness |
|||
Issue descriptionRelevant design document: https://docs.google.com/document/d/1AnsQpiWdtEuacKoYloVktHcX2m2fnuWmuFjiLaijxs4 We want to have the debugger forcibly disable liveness analysis in TurboFan, which is already exposed via the --noanalyze-environment-liveness command line option, in order to improve developer experience. So we should have fuzzer coverage for this configuration as well, like at least the correctness fuzzer should test with this feature disabled to make sure we produce the same results.
,
Apr 5 2018
Yes, pass --noanalyze-environment-liveness and that only makes sense with TurboFan. It's probably useful to combine with --always-opt in a separate config.
,
Apr 5 2018
,
Apr 5 2018
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/adf7ee179117915f024241cb61d56255298fdbbc commit adf7ee179117915f024241cb61d56255298fdbbc Author: Michael Achenbach <machenbach@chromium.org> Date: Thu Apr 05 07:22:34 2018 [foozzie] Add trial for --noanalyze-environment-liveness NOTRY=true Bug: chromium:827067 Change-Id: I05073fd85b8b1b1545d5c2be55676aed237d1c10 Reviewed-on: https://chromium-review.googlesource.com/997292 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#52376} [modify] https://crrev.com/adf7ee179117915f024241cb61d56255298fdbbc/tools/clusterfuzz/v8_foozzie.py
,
Apr 11 2018
Done. Also trial on clusterfuzz... see blocking bug. |
|||
►
Sign in to add a comment |
|||
Comment 1 by machenb...@chromium.org
, Apr 4 2018