diff options
| author | Luke Wagner <mail@lukewagner.name> | 2015-10-06 14:36:01 -0500 |
|---|---|---|
| committer | Luke Wagner <mail@lukewagner.name> | 2015-10-06 14:36:01 -0500 |
| commit | 86c38e0405769e105151dcfa09290681c47d73cc (patch) | |
| tree | 2c665efd20d840ff64d854e403574ad14b791154 /FAQ.md | |
| parent | 8994285386b76b1fd2839946effaad3a36a62037 (diff) | |
| download | nanowasm-design-86c38e0405769e105151dcfa09290681c47d73cc.tar.gz | |
Only allow memory growth in MVP
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -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 |
