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

// Copyright 2016 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: --always-opt

// The rightmost cons string is created first, resulting in an empty left part.
eval(" " + ("" + "try {;} catch (_) {}"));
Allow empty first parts of ConsStrings TurboFan lowering (see [0]) of ConsString creation cannot ensure that the first part of the cons string is non-empty without introducing a phi and negatively impacting performance. This modifies ConsStringIterator to allow empty first parts of ConsStrings. BUG=v8:5440 Review-Url: https://codereview.chromium.org/2377983002 Cr-Commit-Position: refs/heads/master@{#39817} 2016-09-28 09:46:39 +00:00			`// Copyright 2016 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.`

[turbofan] Remove --turbo shorthand for --turbo-filter. This removes the --turbo flag and solely relies on the filter pattern provided via --turbo-filter when deciding whether to use TurboFan. Note that disabling optimization wholesale can still be done with --no-opt, which should be used in favor of --no-turbo everywhere. Also note that this contains semantic changes to the TurboFan activation criteria. We respect the filter pattern more stringently and no longer activate TurboFan just because the source contains patterns forcing use of Ignition via {AstNumberingVisitor::DisableFullCodegenAndCrankshaft}. R=rmcilroy@chromium.org BUG=v8:6408 Change-Id: I0c855f6a62350eb62283a3431c8cc1baa750950e Reviewed-on: https://chromium-review.googlesource.com/528121 Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#46167} 2017-06-22 13:46:04 +00:00			`// Flags: --always-opt`
Allow empty first parts of ConsStrings TurboFan lowering (see [0]) of ConsString creation cannot ensure that the first part of the cons string is non-empty without introducing a phi and negatively impacting performance. This modifies ConsStringIterator to allow empty first parts of ConsStrings. BUG=v8:5440 Review-Url: https://codereview.chromium.org/2377983002 Cr-Commit-Position: refs/heads/master@{#39817} 2016-09-28 09:46:39 +00:00
			`// The rightmost cons string is created first, resulting in an empty left part.`
			`eval(" " + ("" + "try {;} catch (_) {}"));`