[wasm] GrowMemory should update imported memory objects.

[wasm] GrowMemory should update imported memory objects.

When the instance has imported memory, calling GrowMemory should update the memory object to have a consistent view of the memory. This fixes the failing emscripten test case, added a reduced test that simulates the same behavior.

R=titzer@chromium.org, dschuff@chromium.org

Committed: https://crrev.com/5afa8ed77afc9118c5da9bc31c31cae49d2d993e
Cr-Commit-Position: refs/heads/master@{#40490}

[gdeepti, 2016-10-21 05:39:32]

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

[commit-bot: I haz the power, 2016-10-21 05:39:36]

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

[gdeepti, 2016-10-21 05:54:47]

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

[commit-bot: I haz the power, 2016-10-21 05:54:56]

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-10-21 06:26:45]

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

[commit-bot: I haz the power, 2016-10-21 06:26:46]

Dry run: This issue passed the CQ dry run.

[titzer, 2016-10-21 07:51:21]

lgtm, thanks!

[gdeepti, 2016-10-21 08:07:59]

The CQ bit was checked by gdeepti@chromium.org

[commit-bot: I haz the power, 2016-10-21 08:08:13]

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-10-21 08:38:44]

Committed patchset #2 (id:20001)

[Derek Schuff, 2016-10-21 15:49:43]

On 2016/10/21 08:38:44, commit-bot: I haz the power wrote:
> Committed patchset #2 (id:20001)

Cool!
Is there also a test that grows the memory using the grow method on
WebAssembly.Memory?

[gdeepti, 2016-10-21 17:10:36]

On 2016/10/21 15:49:43, Derek Schuff wrote:
> On 2016/10/21 08:38:44, commit-bot: I haz the power wrote:
> > Committed patchset #2 (id:20001)
> 
> Cool!
> Is there also a test that grows the memory using the grow method on
> WebAssembly.Memory?

The two tests above this one in the same file TestGrowMemoryZeroInitialMemory,
TestGrowMemoryMaxDesc both use the grow method on WebAssembly.Memory.

[commit-bot: I haz the power, 2016-11-17 22:09:06]

Description was changed from

==========
[wasm] GrowMemory should update imported memory objects.

When the instance has imported memory, calling GrowMemory should update the
memory object to have a consistent view of the memory. This fixes the failing
emscripten test case, added a reduced test that simulates the same behavior.

R=titzer@chromium.org, dschuff@chromium.org
==========

to

==========
[wasm] GrowMemory should update imported memory objects.

When the instance has imported memory, calling GrowMemory should update the
memory object to have a consistent view of the memory. This fixes the failing
emscripten test case, added a reduced test that simulates the same behavior.

R=titzer@chromium.org, dschuff@chromium.org

Committed: https://crrev.com/5afa8ed77afc9118c5da9bc31c31cae49d2d993e
Cr-Commit-Position: refs/heads/master@{#40490}
==========

[commit-bot: I haz the power, 2016-11-17 22:09:07]

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