v8/test/mjsunit/regress/regress-913844.js

// Copyright 2018 the V8 project authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

// Flags: --disable-in-process-stack-traces --perf-prof-unwinding-info --turbo-loop-rotation
for (var x = 0; x < 1000000; x++)
;
Remove invalid DCHECKS in unwinding-info-writer The unwinding info writer was assuming that a block that had no initial state must be the start or end block. It was trying to check if the block was the start or end by asserting that the block had either no predecessors or no successors. Loop rotation breaks this assumption, since it can move a block from inside a loop to before the loop header, and the block can then be the "start" block. But since such a block has both predecessor(s) and a successor, the check was wrong. R=clemensh@chromium.org BUG=chromium:913844 Change-Id: Ic24c67a822d510cb082f25608089d313c3459be8 Reviewed-on: https://chromium-review.googlesource.com/c/1373770 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#58675} 2019-01-09 14:36:02 +00:00			`// Copyright 2018 the V8 project authors. All rights reserved.`
			`// Use of this source code is governed by a BSD-style license that can be`
			`// found in the LICENSE file.`

[mjsunit] Dont generate dumps from regression test The --perf-prof flag generates unwanted .dump files, while the --perf-prof-unwinding-info flag enables the functionality under test here. R=jgruber@chromium.org BUG=chromium:913844 Change-Id: Ie5ee374977d6105854f42065600dac1bc5ba6df7 Reviewed-on: https://chromium-review.googlesource.com/c/1409363 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#58791} 2019-01-14 14:47:59 +00:00			`// Flags: --disable-in-process-stack-traces --perf-prof-unwinding-info --turbo-loop-rotation`
Remove invalid DCHECKS in unwinding-info-writer The unwinding info writer was assuming that a block that had no initial state must be the start or end block. It was trying to check if the block was the start or end by asserting that the block had either no predecessors or no successors. Loop rotation breaks this assumption, since it can move a block from inside a loop to before the loop header, and the block can then be the "start" block. But since such a block has both predecessor(s) and a successor, the check was wrong. R=clemensh@chromium.org BUG=chromium:913844 Change-Id: Ic24c67a822d510cb082f25608089d313c3459be8 Reviewed-on: https://chromium-review.googlesource.com/c/1373770 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#58675} 2019-01-09 14:36:02 +00:00			`for (var x = 0; x < 1000000; x++)`
			`;`