diff options
| author | JF Bastien <jfb@chromium.org> | 2015-06-09 18:16:04 +0200 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2015-06-09 18:16:04 +0200 |
| commit | fc88967d7bb150a3a82101d631025fa6da7d24ee (patch) | |
| tree | ecb84fd185c5c9a11c52c1db28e08c8f0319b036 /FutureFeatures.md | |
| parent | 82bd80a0613f269bf3293013c0b953eb8f69140d (diff) | |
| download | nanowasm-design-fc88967d7bb150a3a82101d631025fa6da7d24ee.tar.gz | |
Clarify 64-bit heap.
Diffstat (limited to 'FutureFeatures.md')
| -rw-r--r-- | FutureFeatures.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/FutureFeatures.md b/FutureFeatures.md index 0653d1d..0e23e39 100644 --- a/FutureFeatures.md +++ b/FutureFeatures.md @@ -72,9 +72,9 @@ WebAssembly will eventually allow heaps greater than 4GiB by providing load/store operations that take 64-bit address operands. Modules which opt-in to this feature have `int64` as the canonical pointer type. -On a 32-bit system, heaps must still be smaller than 4GiB. All 64-bit pointer -arithmetic arithmetic (which will be much slower than 32-bit arithmetic) will be -therefore unnecessary. +On a 32-bit system, heaps must still be smaller than 4GiB. A WebAssembly +implementation running on such a platform may restrict allocations to the lower +4GiB, and leave the two 32-bits untouched. ## Source maps integration |