Add foozzie config for Liftoff |
|||
Issue description
We already had a few miscompilations in Liftoff which did not lead to crashes, but produced wrong output. It would be nice to let Foozzie catch some of those.
Is adding a foozzie config as easy as this, or are additional steps needed?
--- a/tools/clusterfuzz/v8_foozzie.py
+++ b/tools/clusterfuzz/v8_foozzie.py
@@ -56,6 +56,9 @@ CONFIGS = dict(
'--no-lazy-inner-functions',
'--suppress-asm-messages',
],
+ liftoff=[
+ '--liftoff',
+ ],
slow_path=[
'--force-slow-path',
'--suppress-asm-messages',
,
Mar 21 2018
,
Mar 21 2018
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/49f23ce6425252a589f0e756be70d2d1224b70c2 commit 49f23ce6425252a589f0e756be70d2d1224b70c2 Author: Clemens Hammacher <clemensh@chromium.org> Date: Wed Mar 21 12:56:18 2018 [foozzie] Add Liftoff testing This adds 5% testing of 'ignition' vs 'liftoff', which tests Turbofan vs Liftoff for wasm code, and tests Ignition vs Turbofan for javascript code. It also adds 3% testing of 'liftoff' (x64) vs 'liftoff' (ia32), which does standard x64 vs ia32 testing for javascript code. R=machenbach@chromium.org Bug: chromium:824098 , v8:6600 Change-Id: I6a6afae0300efc33f3535541a11695a7bb32dcc5 Reviewed-on: https://chromium-review.googlesource.com/973161 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#52111} [modify] https://crrev.com/49f23ce6425252a589f0e756be70d2d1224b70c2/tools/clusterfuzz/v8_foozzie.py [modify] https://crrev.com/49f23ce6425252a589f0e756be70d2d1224b70c2/tools/clusterfuzz/v8_foozzie_test.py [modify] https://crrev.com/49f23ce6425252a589f0e756be70d2d1224b70c2/tools/clusterfuzz/v8_fuzz_config.py
,
Mar 21 2018
,
Jul 19
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/605f94b70077ab0c8a4d79ffbb33686883157932 commit 605f94b70077ab0c8a4d79ffbb33686883157932 Author: Clemens Hammacher <clemensh@chromium.org> Date: Thu Jul 19 09:51:06 2018 [foozzie] Update existing configs for liftoff Instead of having a separate liftoff config, which is tested against the default (which currently means tier-up from liftoff to turbofan), just choose reasonable liftoff configs for the existing configs. 'ignition' now implies pure liftoff execution. 'ignition_turbo_opt' always compiles with turbofan. Other configs use the default (tier up). R=machenbach@chromium.org Bug: chromium:824098 , v8:6600 Change-Id: I92c008fc1b1fa54d3161fb5695a095127d6ac263 Reviewed-on: https://chromium-review.googlesource.com/1141731 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#54548} [modify] https://crrev.com/605f94b70077ab0c8a4d79ffbb33686883157932/tools/clusterfuzz/testdata/failure_output.txt [modify] https://crrev.com/605f94b70077ab0c8a4d79ffbb33686883157932/tools/clusterfuzz/v8_foozzie.py [modify] https://crrev.com/605f94b70077ab0c8a4d79ffbb33686883157932/tools/clusterfuzz/v8_foozzie_test.py [modify] https://crrev.com/605f94b70077ab0c8a4d79ffbb33686883157932/tools/clusterfuzz/v8_fuzz_config.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by machenb...@chromium.org
, Mar 21 2018Status: Assigned (was: Available)