[serializer] allocate global proxy with the expected size.

[serializer] allocate global proxy with the expected size.

If a context snapshot includes the global proxy constructor function, we
expect the incoming global proxy to have the correct instance size so
that we can reinitialize it with said constructor. However, when the
bootstrapper allocates a new global proxy, we need to know the expected
size.

We solve this by storing the size on the to-be-serialized isolate.

R=jochen@chromium.org, peria@chromium.org
BUG=chromium:617892
Review-Url: https://codereview.chromium.org/2585693002
Cr-Commit-Position: refs/heads/master@{#41756}
Committed: https://chromium.googlesource.com/v8/v8/+/55e8c2e4d3c5f79295a7bfb1ca929e14541f28fe

[Yang, 2016-12-16 10:01:57]

The CQ bit was checked by yangguo@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-16 10:02:05]

Dry run: 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-12-16 10:32:44]

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

[commit-bot: I haz the power, 2016-12-16 10:32:45]

Dry run: This issue passed the CQ dry run.

[Yang, 2016-12-16 11:51:13]

On 2016/12/16 09:22:28, Yang wrote:

Can I haz review? :)

[jochen (gone - plz use gerrit), 2016-12-16 11:59:23]

lgtm

[Yang, 2016-12-16 11:59:50]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2016-12-16 11:59:54]

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-12-16 12:40:40]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481889590564490, "parent_rev":
"a492ab38197616be2d62e050dde554c57695508e", "commit_rev":
"55e8c2e4d3c5f79295a7bfb1ca929e14541f28fe"}

[commit-bot: I haz the power, 2016-12-16 12:40:43]

Description was changed from

==========
[serializer] allocate global proxy with the expected size.

If a context snapshot includes the global proxy constructor function, we
expect the incoming global proxy to have the correct instance size so
that we can reinitialize it with said constructor. However, when the
bootstrapper allocates a new global proxy, we need to know the expected
size.

We solve this by storing the size on the to-be-serialized isolate.

R=jochen@chromium.org, peria@chromium.org
BUG=chromium:617892
==========

to

==========
[serializer] allocate global proxy with the expected size.

If a context snapshot includes the global proxy constructor function, we
expect the incoming global proxy to have the correct instance size so
that we can reinitialize it with said constructor. However, when the
bootstrapper allocates a new global proxy, we need to know the expected
size.

We solve this by storing the size on the to-be-serialized isolate.

R=jochen@chromium.org, peria@chromium.org
BUG=chromium:617892

Review-Url: https://codereview.chromium.org/2585693002
Cr-Commit-Position: refs/heads/master@{#41756}
Committed:
https://chromium.googlesource.com/v8/v8/+/55e8c2e4d3c5f79295a7bfb1ca929e14541...
==========

[commit-bot: I haz the power, 2016-12-16 12:40:44]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/55e8c2e4d3c5f79295a7bfb1ca929e14541...

[peria, 2016-12-18 16:58:15]

lgtm