From 86c38e0405769e105151dcfa09290681c47d73cc Mon Sep 17 00:00:00 2001 From: Luke Wagner Date: Tue, 6 Oct 2015 14:36:01 -0500 Subject: Only allow memory growth in MVP --- FAQ.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'FAQ.md') diff --git a/FAQ.md b/FAQ.md index 7c7b9b3..8f1e48d 100644 --- a/FAQ.md +++ b/FAQ.md @@ -236,11 +236,11 @@ The [`mmap`](http://pubs.opengroup.org/onlinepubs/009695399/functions/mmap.html) syscall has many useful features. While these are all packed into one overloaded syscall in POSIX, WebAssembly unpacks this functionality into multiple builtins: -* the MVP starts with the ability to resize linear memory via a - [`resize_memory`](AstSemantics.md#resizing) builtin operation; +* the MVP starts with the ability to grow linear memory via a + [`grow_memory`](AstSemantics.md#resizing) builtin operation; * proposed [future features](FutureFeatures.md#finer-grained-control-over-memory) would allow the application to change the protection and mappings for pages - in the contiguous range set by `resize_memory`. + in the contiguous range `[0, memory_size)`. A significant feature of `mmap` that is missing from the above list is the ability to allocate disjoint virtual address ranges. The reasoning for this -- cgit v1.2.3