- 03 Jan, 2017 1 commit
-
-
marja authored
This is another attempt at solving v8:5736; the previous one (r 41723) regressed code load. BUG=v8:5736 R=adamk@chromium.org Review-Url: https://codereview.chromium.org/2583163002 Cr-Commit-Position: refs/heads/master@{#42049}
-
- 20 Dec, 2016 1 commit
-
-
littledan authored
eval() may introduce a scope which needs to be represented as a context at runtime, e.g., eval('var x; let y; ()=>y') introduces a variable y which needs to have a context allocated for it. However, when traversing upwards to find the declaration context for a variable which leaks, as the declaration of x does above, this context has to be understood to not be a declaration context in sloppy mode. This patch makes that distinction by introducing a different map for eval-introduced contexts. A dynamic search for the appropriate context will continue past an eval context to find the appropriate context. Marking contexts as eval contexts rather than function contexts required updates in each compiler backend. BUG=v8:5295, chromium:648719 Review-Url: https://codereview.chromium.org/2435023002 Cr-Commit-Position: refs/heads/master@{#41869}
-
- 15 Dec, 2016 1 commit
-
-
marja authored
If the eval contains a let, we need to know whether an inner function refers to the variable to be able to decide its context allocation status. The added test needs https://codereview.chromium.org/2435023002/ too in order to pass. BUG=v8:5736 Review-Url: https://codereview.chromium.org/2574753002 Cr-Commit-Position: refs/heads/master@{#41723}
-