CanElideLastBasedOnSourcePosition(node) in bytecode-peephole-optimizer.cc |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6292713431629824 Fuzzer: decoder_langfuzz Job Type: linux_asan_d8_ignition_v8_arm_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: CanElideLastBasedOnSourcePosition(node) in bytecode-peephole-optimizer.cc Regressed: V8: r37865:37866 Minimized Testcase (6.40 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96k8SQNl4MSeh4ACsgT-AvsFbPVxfbBM1G3xlSMB1Q6K4Rj-lmEu4cFeqC8TAh7W5UfHux-T4xecU61baGvBRwZgsKWr4IFzuMudsConNRQYr11yUU10zU-_UmBeHxVz88V7sRVMWXWgD51Rae8bE9-ZqWJFQ?testcase_id=6292713431629824 Filer: mstarzinger See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/02b0985335708736223218289e9a4589d927905d commit 02b0985335708736223218289e9a4589d927905d Author: oth <oth@chromium.org> Date: Thu Jul 28 14:41:15 2016 [interpreter] Fix peephole rule on eliding last before jump. BUG= chromium:629792 LOG=N Review-Url: https://codereview.chromium.org/2185123003 Cr-Commit-Position: refs/heads/master@{#38140} [modify] https://crrev.com/02b0985335708736223218289e9a4589d927905d/src/interpreter/bytecode-peephole-optimizer.cc [add] https://crrev.com/02b0985335708736223218289e9a4589d927905d/test/mjsunit/ignition/regress-629792-source-position-on-jump.js
,
Jul 31 2016
ClusterFuzz has detected this issue as fixed in range 38139:38140. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6292713431629824 Fuzzer: decoder_langfuzz Job Type: linux_asan_d8_ignition_v8_arm_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: CanElideLastBasedOnSourcePosition(node) in bytecode-peephole-optimizer.cc Regressed: V8: r37865:37866 Fixed: V8: r38139:38140 Minimized Testcase (6.40 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96k8SQNl4MSeh4ACsgT-AvsFbPVxfbBM1G3xlSMB1Q6K4Rj-lmEu4cFeqC8TAh7W5UfHux-T4xecU61baGvBRwZgsKWr4IFzuMudsConNRQYr11yUU10zU-_UmBeHxVz88V7sRVMWXWgD51Rae8bE9-ZqWJFQ?testcase_id=6292713431629824 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jul 31 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by mstarzinger@chromium.org
, Jul 20 2016Owner: oth@chromium.org
Status: Assigned (was: Available)
Regression range points to table based peephole optimizer. Reproduces as follows ... $ ./out/x64.debug/d8 --ignition mutant1217_regress-3650-1.js $ cat mutant1217_regress-3650-1.js function f(t) { var f = t || this; for (var i in t) { for (var j in t) { (j); continue; } } return eval.join(''); } f();