diff options
| author | titzer <titzer@google.com> | 2015-06-23 13:08:17 +0200 |
|---|---|---|
| committer | titzer <titzer@google.com> | 2015-06-23 13:08:17 +0200 |
| commit | fa95fdddf9c034235a320e8df12810af6baa747a (patch) | |
| tree | 93edd26a497ec4e2e55dff05ee4f9ed3af6c4b66 | |
| parent | 2702652ef428433ded065e44b623cd4f016da117 (diff) | |
| download | nanowasm-design-fa95fdddf9c034235a320e8df12810af6baa747a.tar.gz | |
Update AstSemantics.md
| -rw-r--r-- | AstSemantics.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/AstSemantics.md b/AstSemantics.md index 4dfa245..6a60c60 100644 --- a/AstSemantics.md +++ b/AstSemantics.md @@ -146,7 +146,7 @@ nested. This guarantees that all resulting control flow graphs are well-structur Programs address the heap by using integers that are interpreted as unsigned byte indexes starting at `0`. Accesses to the heap at indices larger than the size of the heap are considered out-of-bounds, -and a module may optionally define that out-of-bounds includes small indices close to `0` (see https://github.com/WebAssembly/design/issues/204). +and a module may optionally define that out-of-bounds includes small indices close to `0` (see [discussion] (https://github.com/WebAssembly/design/issues/204)). Out-of-bounds access is considered a program error, and the semantics are discussed below. Each heap access is annotated with a *Memory type* and the presumed alignment of the index. |