Fix lazy parsing for functions that use super.

Fix lazy parsing for functions that use super.

The preparser needs to log the usage of super properties and then update
the scope when we create the function later.

BUG=v8:3888
LOG=N
R=dslomov@chromium.org, marja

Committed: https://crrev.com/765e002a4fce831c91393db6c1d464ef3f1264f5
Cr-Commit-Position: refs/heads/master@{#26642}

[arv (Not doing code reviews), 2015-02-12 20:03:15]

cleanup

[arv (Not doing code reviews), 2015-02-12 20:07:28]

PTAL

Marja: Just to be sure, since this change does not change the headers of
PreparseDataConstants there is no need to increment the version, right?

[Dmitry Lomov (no reviews), 2015-02-12 20:11:33]

lgtm but no idea about versioning

[marja, 2015-02-13 17:12:05]

On 2015/02/12 20:07:28, arv wrote:
> PTAL
> 
> Marja: Just to be sure, since this change does not change the headers of
> PreparseDataConstants there is no need to increment the version, right?

Data produced by the old version is not readable by the new version, and vice
versa, so the version should change too.

Though, Blink also guards against giving V8 data produced by a previous version
by tagging the cached data with V8 version. But purely from V8's point of view,
it makes sense to change the version when making incompatible changes to the
data format.

[marja, 2015-02-13 17:12:19]

(otherwise lgtm)

[arv (Not doing code reviews), 2015-02-13 17:46:33]

On 2015/02/13 at 17:12:05, marja wrote:
> On 2015/02/12 20:07:28, arv wrote:
> > PTAL
> > 
> > Marja: Just to be sure, since this change does not change the headers of
> > PreparseDataConstants there is no need to increment the version, right?
> 
> Data produced by the old version is not readable by the new version, and vice
versa, so the version should change too.
> 
> Though, Blink also guards against giving V8 data produced by a previous
version by tagging the cached data with V8 version. But purely from V8's point
of view, it makes sense to change the version when making incompatible changes
to the data format.

Thanks. It wasn't clear to me that this is an incompatible change.

[arv (Not doing code reviews), 2015-02-13 17:50:19]

New patchsets have been uploaded after l-g-t-m from
dslomov@chromium.org,marja@chromium.org

[arv (Not doing code reviews), 2015-02-13 17:50:21]

Increment the PreparserData version

[arv (Not doing code reviews), 2015-02-13 17:50:56]

The CQ bit was checked by arv@chromium.org

[commit-bot: I haz the power, 2015-02-13 17:51:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/923683002/40001

[commit-bot: I haz the power, 2015-02-13 18:34:57]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-02-13 18:35:18]

Patchset 3 (id:??) landed as
https://crrev.com/765e002a4fce831c91393db6c1d464ef3f1264f5
Cr-Commit-Position: refs/heads/master@{#26642}