Reland: [modules] Properly initialize declared variables.

Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Committed: https://crrev.com/427242326cdb322fd8d6df1f80bb3f4a24733708
Cr-Original-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Original-Commit-Position: refs/heads/master@{#39892}
Cr-Commit-Position: refs/heads/master@{#39900}

[neis, 2016-09-27 23:10:20]

Please take a first look.

[adamk, 2016-09-27 23:26:13]

Very clean indeed. lgtm with more CL description.

https://codereview.chromium.org/2375793002/diff/1/src/parsing/parser.cc
File src/parsing/parser.cc (right):

https://codereview.chromium.org/2375793002/diff/1/src/parsing/parser.cc#newco...
src/parsing/parser.cc:2600: this->scope()->ForceContextAllocation();
Nit: remove "this->"

[neis, 2016-09-29 11:42:33]

Description was changed from

==========
"Modules are generators."

R=adamk@chromium.org
BUG=
==========

to

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
==========

[neis, 2016-09-29 11:43:57]

On 2016/09/27 23:26:13, adamk wrote:
> Very clean indeed. lgtm with more CL description.
> 
> https://codereview.chromium.org/2375793002/diff/1/src/parsing/parser.cc
> File src/parsing/parser.cc (right):
> 
>
https://codereview.chromium.org/2375793002/diff/1/src/parsing/parser.cc#newco...
> src/parsing/parser.cc:2600: this->scope()->ForceContextAllocation();
> Nit: remove "this->"

Done.

Also changed the CL description, and installed an internal version of
generator-next that doesn't show up in the stack trace.

[neis, 2016-09-29 11:44:27]

neis@chromium.org changed reviewers:
+ mstarzinger@chromium.org

[neis, 2016-09-29 11:44:27]

+mstarzinger for interpreter

[Michael Starzinger, 2016-09-29 12:30:26]

LGTM on "interpreter", didn't look at the rest.

[neis, 2016-09-29 12:37:03]

The CQ bit was checked by neis@chromium.org

[neis, 2016-09-29 12:37:03]

The patchset sent to the CQ was uploaded after l-g-t-m from adamk@chromium.org
Link to the patchset: https://codereview.chromium.org/2375793002/#ps60001
(title: "Address comment and remove bogus comment.")

[commit-bot: I haz the power, 2016-09-29 12:37:14]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 13:09:59]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-29 13:10:00]

Try jobs failed on following builders:
  v8_linux_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng/builds/13674)
  v8_linux_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng_triggered/b...)

[neis, 2016-09-29 13:14:54]

Ok, I need to introduce a new FunctionKind after all.

[Michael Starzinger, 2016-09-29 13:46:43]

LGTM on patch set #4 from my end as well.

[neis, 2016-09-29 13:47:57]

The CQ bit was checked by neis@chromium.org

[neis, 2016-09-29 13:47:57]

The patchset sent to the CQ was uploaded after l-g-t-m from adamk@chromium.org
Link to the patchset: https://codereview.chromium.org/2375793002/#ps80001
(title: "Use new FunctionKind::kModule rather than kGeneratorFunction.")

[Michael Starzinger, 2016-09-29 13:48:00]

Doesn't SharedFunctionInfo::is_resumable need to be adapted though?

[commit-bot: I haz the power, 2016-09-29 13:48:01]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 14:20:37]

Description was changed from

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
==========

to

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
==========

[commit-bot: I haz the power, 2016-09-29 14:20:38]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-09-29 14:21:08]

Description was changed from

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
==========

to

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

[commit-bot: I haz the power, 2016-09-29 14:21:09]

Patchset 5 (id:??) landed as
https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}

[Michael Achenbach, 2016-09-29 15:09:43]

A revert of this CL (patchset #5 id:80001) has been created in
https://codereview.chromium.org/2379063002/ by machenbach@chromium.org.

The reason for reverting is: Suspect for causing win64 debug problems:
https://build.chromium.org/p/client.v8/builders/V8%20Win64%20-%20debug/builds....

[neis, 2016-09-29 15:24:41]

Description was changed from

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

to

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

[neis, 2016-09-29 18:03:36]

Description was changed from

==========
[modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

[neis, 2016-09-29 18:03:48]

The CQ bit was checked by neis@chromium.org

[neis, 2016-09-29 18:03:49]

The patchset sent to the CQ was uploaded after l-g-t-m from adamk@chromium.org,
mstarzinger@chromium.org
Link to the patchset: https://codereview.chromium.org/2375793002/#ps100001
(title: "Update CompilerHints.")

[commit-bot: I haz the power, 2016-09-29 18:03:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Michael Achenbach, 2016-09-29 18:05:39]

The CQ bit was unchecked by machenbach@chromium.org

[Michael Achenbach, 2016-09-29 18:05:58]

On 2016/09/29 18:03:51, commit-bot: I haz the power wrote:
> CQ is trying da patch. Follow status at
>  
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

What about the win dbg failures?
https://build.chromium.org/p/tryserver.v8/builders/v8_win_dbg/builds/409

[Michael Achenbach, 2016-09-29 18:07:16]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

[Michael Achenbach, 2016-09-29 18:07:43]

On 2016/09/29 18:05:58, machenbach (slow) wrote:
> On 2016/09/29 18:03:51, commit-bot: I haz the power wrote:
> > CQ is trying da patch. Follow status at
> >  
> >
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
> 
> What about the win dbg failures?
> https://build.chromium.org/p/tryserver.v8/builders/v8_win_dbg/builds/409

Added a line to the CL desc that enforces running this bot on CQ.

[Michael Achenbach, 2016-09-29 18:07:59]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2016-09-29 18:08:11]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[neis, 2016-09-29 18:10:19]

The CQ bit was unchecked by neis@chromium.org

[neis, 2016-09-29 18:35:12]

The CQ bit was checked by neis@chromium.org

[commit-bot: I haz the power, 2016-09-29 18:35:16]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 19:31:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-29 19:31:41]

Try jobs failed on following builders:
  v8_linux_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng/builds/13717)
  v8_linux_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng_triggered/b...)

[neis, 2016-09-29 19:51:36]

The CQ bit was checked by neis@chromium.org

[commit-bot: I haz the power, 2016-09-29 19:51:44]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 20:43:35]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-29 20:43:36]

Try jobs failed on following builders:
  v8_linux_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng/builds/13720)
  v8_linux_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng_triggered/b...)

[adamk, 2016-09-29 20:47:49]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2016-09-29 20:47:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 21:34:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-29 21:34:41]

Try jobs failed on following builders:
  v8_linux_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng/builds/13725)
  v8_linux_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng_triggered/b...)

[adamk, 2016-09-29 21:57:34]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2016-09-29 21:57:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 22:24:43]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

[commit-bot: I haz the power, 2016-09-29 22:24:44]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2016-09-29 22:25:07]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Cr-Commit-Position: refs/heads/master@{#39871}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

[commit-bot: I haz the power, 2016-09-29 22:25:08]

Patchset 6 (id:??) landed as
https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Commit-Position: refs/heads/master@{#39892}

[Benedikt Meurer, 2016-09-30 04:21:54]

A revert of this CL (patchset #6 id:100001) has been created in
https://codereview.chromium.org/2387593002/ by bmeurer@chromium.org.

The reason for reverting is: Speculative revert for christmas tree.

[Michael Achenbach, 2016-09-30 06:41:16]

Very strange: The problems seemed to have started with this CL again, stopped on
revert, but there's this one after the revert:
https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20debug/builds...

[neis, 2016-09-30 07:50:34]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

[neis, 2016-09-30 07:50:43]

The CQ bit was checked by neis@chromium.org

[commit-bot: I haz the power, 2016-09-30 07:50:47]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-30 07:53:47]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

[commit-bot: I haz the power, 2016-09-30 07:53:49]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2016-09-30 07:54:05]

Description was changed from

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Cr-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Commit-Position: refs/heads/master@{#39892}
==========

to

==========
Reland: [modules] Properly initialize declared variables.

Before evaluating a module, all variables declared at the top-level
in _any_ of the modules in the dependency graph must be initialized.
This is observable because a module A can access a variable imported
from module B (e.g. a function) at a point when module B's body hasn't
been evaluated yet.

We achieve this by implementing modules internally as generators with
two states (not initialized, initialized).

R=adamk@chromium.org
BUG=v8:1569
CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_win_dbg

Committed: https://crrev.com/f4dfb6fbe1cdd9a0f287a1a9c496e1f69f6f5d20
Committed: https://crrev.com/8c52a411583e870bd5ed100864caa58f491c5d88
Committed: https://crrev.com/427242326cdb322fd8d6df1f80bb3f4a24733708
Cr-Original-Original-Commit-Position: refs/heads/master@{#39871}
Cr-Original-Commit-Position: refs/heads/master@{#39892}
Cr-Commit-Position: refs/heads/master@{#39900}
==========

[commit-bot: I haz the power, 2016-09-30 07:54:12]

Patchset 6 (id:??) landed as
https://crrev.com/427242326cdb322fd8d6df1f80bb3f4a24733708
Cr-Commit-Position: refs/heads/master@{#39900}