75f2d65f00
Scope analysis is over-conservative when treating variable resolutions as possibly-shadowed by a sloppy eval. In the attached bug, this comes into play since catch scopes have different behavior with respect to the "calls eval" in eager vs lazy compilation (in the latter, they are never marked as "calls eval" because CatchContexts don't have an associated ScopeInfo). This patch changes the scope-type check to also eliminate a few other cases where shadowing isn't possible, such as non-declaration block scopes. BUG=chromium:608279 LOG=n Review-Url: https://codereview.chromium.org/1950803002 Cr-Commit-Position: refs/heads/master@{#36046}
19 lines
412 B
JavaScript
19 lines
412 B
JavaScript
// 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 --no-lazy
|
|
|
|
function __f_38() {
|
|
try {
|
|
throw 0;
|
|
} catch (e) {
|
|
eval();
|
|
var __v_38 = { a: 'hest' };
|
|
__v_38.m = function () { return __v_38.a; };
|
|
}
|
|
return __v_38;
|
|
}
|
|
var __v_40 = __f_38();
|
|
__v_40.m();
|