diff options
| author | JF Bastien <jfb@chromium.org> | 2015-06-09 16:04:44 +0200 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2015-06-09 16:05:21 +0200 |
| commit | 4c797055b4d42b5a0b7b68d0b08ca32c8ab092bf (patch) | |
| tree | 5a4491948d0dc3cf73a657aff9e396bf15fc27a7 | |
| parent | 3f83acabd167609e0982f5fbbdb817ab2cf759d8 (diff) | |
| download | nanowasm-design-4c797055b4d42b5a0b7b68d0b08ca32c8ab092bf.tar.gz | |
Clarify tier 1.
| -rw-r--r-- | Portability.md | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/Portability.md b/Portability.md index 7b2804a..ff31159 100644 --- a/Portability.md +++ b/Portability.md @@ -2,10 +2,13 @@ WebAssembly's [binary format](BinaryEncoding.md) is designed to be executable efficiently on a variety of operating systems and instruction set architectures, -[on the web](Web.md) and [off the web](NonWeb.md). The standardization process -will identify *tier 1* platforms on which WebAssembly is expected to be -implementable efficiently in a fully conformant manner, taking into account -[allowed implementation variants](IncompletelySpecifiedBehavior.md). +[on the web](Web.md) and [off the web](NonWeb.md). + +The standardization process will identify *tier 1* platforms on which +WebAssembly is expected to be implementable efficiently in a fully conformant +manner, taking into account +[allowed implementation variants](IncompletelySpecifiedBehavior.md). These tier +1 platforms will guide WebAssembly's definition of portability. WebAssembly portability assumes that execution environments offer the following characteristics: |