From 2c740481c4862fc58b9e99e16652c2e1dccbf786 Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Wed, 10 Jun 2015 09:48:07 -0700 Subject: Clarify that implementations don't actually need to make 4 GiB of memory available. And that >4GiB heaps will be a feature-tested feature. --- Portability.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Portability.md b/Portability.md index 9b4387b..7a116f3 100644 --- a/Portability.md +++ b/Portability.md @@ -24,9 +24,12 @@ characteristics: * Support unaligned memory accesses or reliable trapping that allows software emulation thereof. * Little-endian byte ordering. -* Up to 4GiB of addressable memory in a 32-bit address space. Heaps bigger than - 4GiB in a 64-bit address space - [may be added later](FutureFeatures.md#Heaps-bigger-than-4GiB). +* Memory regions which can be efficiently addressed with 32-bit + pointers or indices. +* Heaps bigger than 4GiB with 64-bit addressing + [may be added later](FutureFeatures.md#Heaps-bigger-than-4GiB), though it will + be done under a [feature test](FeatureTest.md) so it won't be required for all + WebAssembly implementations. * Enforce secure isolation between WebAssembly modules and other modules or processes executing on the same machine. * An execution environment which offers forward progress guarantees to all -- cgit v1.2.3