Separate module min memory pages counter for asm.js/WASM.

Separate module min memory pages counter for asm.js/WASM.

Currently, V8 uses the same size counter to measure the minimum number of memory pages allocated by a module for both asm.js and WASM. This CL separates the counter into two separate counters, and then uses the appropriate counter when measuring.

BUG=chromium:704922
R=mtrofin@chromium.org,bradnelson@chromium.org

Review-Url: https://codereview.chromium.org/2781453004
Cr-Commit-Position: refs/heads/master@{#44204}
Committed: https://chromium.googlesource.com/v8/v8/+/1d4821280b2e09292e80d873dfff816939809c69

[kschimpf, 2017-03-28 16:06:50]

Description was changed from

==========
Separate module min memory pages counter for asm.js/WASM.

Currently, V8 uses the same size counter to measure the minimum number of memory
pages allocated by a module for both asm.js and WASM. This CL separatess the
counter into two separate counters, and then uses the appropriate counter when
measuring.

BUG=chromium:704922
==========

to

==========
Separate module min memory pages counter for asm.js/WASM.

Currently, V8 uses the same size counter to measure the minimum number of memory
pages allocated by a module for both asm.js and WASM. This CL separates the
counter into two separate counters, and then uses the appropriate counter when
measuring.

BUG=chromium:704922
R=mtrofin@chromium.org,bradnelson@chromium.org
==========

[kschimpf, 2017-03-28 16:06:50]

kschimpf@chromium.org changed reviewers:
+ bradnelson@chromium.org, mtrofin@chromium.org

[kschimpf, 2017-03-28 16:06:58]

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

[commit-bot: I haz the power, 2017-03-28 16:07:09]

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

[kschimpf, 2017-03-28 16:07:11]

Please review. Thanks!

[commit-bot: I haz the power, 2017-03-28 16:30:39]

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

[commit-bot: I haz the power, 2017-03-28 16:30:40]

Dry run: This issue passed the CQ dry run.

[bradnelson, 2017-03-28 18:12:51]

The CQ bit was checked by bradnelson@chromium.org

[bradnelson, 2017-03-28 18:12:51]

lgtm

[commit-bot: I haz the power, 2017-03-28 18:13: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, 2017-03-28 18:14:13]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490724771567520, "parent_rev":
"a84da1c3b7fcb44ade1d49d97b8c51ba2d89a8f7", "commit_rev":
"1d4821280b2e09292e80d873dfff816939809c69"}

[commit-bot: I haz the power, 2017-03-28 18:14:19]

Description was changed from

==========
Separate module min memory pages counter for asm.js/WASM.

Currently, V8 uses the same size counter to measure the minimum number of memory
pages allocated by a module for both asm.js and WASM. This CL separates the
counter into two separate counters, and then uses the appropriate counter when
measuring.

BUG=chromium:704922
R=mtrofin@chromium.org,bradnelson@chromium.org
==========

to

==========
Separate module min memory pages counter for asm.js/WASM.

Currently, V8 uses the same size counter to measure the minimum number of memory
pages allocated by a module for both asm.js and WASM. This CL separates the
counter into two separate counters, and then uses the appropriate counter when
measuring.

BUG=chromium:704922
R=mtrofin@chromium.org,bradnelson@chromium.org

Review-Url: https://codereview.chromium.org/2781453004
Cr-Commit-Position: refs/heads/master@{#44204}
Committed:
https://chromium.googlesource.com/v8/v8/+/1d4821280b2e09292e80d873dfff8169398...
==========

[commit-bot: I haz the power, 2017-03-28 18:14:20]

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