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

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

Currently, V* uses the same size counter to measure the maximum 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/2783713002
Cr-Commit-Position: refs/heads/master@{#44210}
Committed: https://chromium.googlesource.com/v8/v8/+/90c12512d9f79ab9603db86d228df200e581880b

[kschimpf, 2017-03-28 16:24:51]

Description was changed from

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

Currently, V* uses the same size counter to measure the maximum 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
==========

to

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

Currently, V* uses the same size counter to measure the maximum 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
==========

[kschimpf, 2017-03-28 16:24:51]

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

[kschimpf, 2017-03-28 16:25:47]

Description was changed from

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

Currently, V* uses the same size counter to measure the maximum 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
==========

to

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

Currently, V* uses the same size counter to measure the maximum 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:26:11]

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:26:19]

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:26:27]

Please review. Thanks.

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

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

[commit-bot: I haz the power, 2017-03-28 16:52:04]

Dry run: This issue passed the CQ dry run.

[bradnelson, 2017-03-28 18:13:40]

The CQ bit was checked by bradnelson@chromium.org

[bradnelson, 2017-03-28 18:13:40]

lgtm

[commit-bot: I haz the power, 2017-03-28 18:13:49]

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:19:39]

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

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

Try jobs failed on following builders:
  v8_presubmit on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/37875)

[kschimpf, 2017-03-28 20:09:09]

The CQ bit was checked by kschimpf@chromium.org

[kschimpf, 2017-03-28 20:09:10]

The patchset sent to the CQ was uploaded after l-g-t-m from
bradnelson@chromium.org
Link to the patchset: https://codereview.chromium.org/2783713002/#ps20001
(title: "Fix merge conflicts with master")

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

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 21:22:17]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1490731749764030,
"parent_rev": "b6bbf6821b156ce84bb9c8a6df8f8471e50b4e7c", "commit_rev":
"90c12512d9f79ab9603db86d228df200e581880b"}

[commit-bot: I haz the power, 2017-03-28 21:22:24]

Description was changed from

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

Currently, V* uses the same size counter to measure the maximum 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 max memory pages counter for asm.js/WASM.

Currently, V* uses the same size counter to measure the maximum 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/2783713002
Cr-Commit-Position: refs/heads/master@{#44210}
Committed:
https://chromium.googlesource.com/v8/v8/+/90c12512d9f79ab9603db86d228df200e58...
==========

[commit-bot: I haz the power, 2017-03-28 21:22:25]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/v8/v8/+/90c12512d9f79ab9603db86d228df200e58...