diff options
| -rw-r--r-- | AstSemantics.md | 2 | ||||
| -rw-r--r-- | BinaryEncoding.md | 2 | ||||
| -rw-r--r-- | FAQ.md | 3 | ||||
| -rw-r--r-- | FeatureTest.md | 2 |
4 files changed, 4 insertions, 5 deletions
diff --git a/AstSemantics.md b/AstSemantics.md index c7a703e..8e6a9bd 100644 --- a/AstSemantics.md +++ b/AstSemantics.md @@ -130,7 +130,7 @@ which leads to the following advantages: splitting, which can reduce throughput overhead, at the cost of increasing code size (potentially very significantly in pathological cases). * The - [signature-restricted proper tail-call](https://github.com/WebAssembly/spec/blob/master/EssentialPostMVPFeatures.md#signature-restricted-proper-tail-calls) + [signature-restricted proper tail-call](EssentialPostMVPFeatures.md#signature-restricted-proper-tail-calls) feature would allow efficient compilation of arbitrary irreducible control flow. diff --git a/BinaryEncoding.md b/BinaryEncoding.md index 00d0cc9..97a143f 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -18,7 +18,7 @@ Reducing download size, is achieved through three layers: * We can do better than generic compression because we are aware of the AST structure and other details: * For example, macro compression that - [deduplicates AST trees](https://github.com/WebAssembly/spec/issues/58#issuecomment-101863032) + [deduplicates AST trees](https://github.com/WebAssembly/design/issues/58#issuecomment-101863032) can focus on AST nodes + their children, thus having `O(nodes)` entities to worry about, compared to generic compression which in principle would need to look at `O(bytes*bytes)` entities. Such macros would allow the @@ -89,8 +89,7 @@ learning and teaching purposes. In fact, by dropping all the [coercions required validation](http://asmjs.org/spec/latest/#introduction), the WebAssembly text format should be much more natural to read and write than asm.js. Outside the browser, command-line and online tools that convert between text and binary will also be made readily available. Lastly, a scalable form of -source maps is also being considered as part of the WebAssembly [tooling story] -(https://github.com/WebAssembly/spec/blob/master/Tooling.md). +source maps is also being considered as part of the WebAssembly [tooling story](Tooling.md). ## What's the story for Emscripten users? diff --git a/FeatureTest.md b/FeatureTest.md index f9877dc..cd6ca34 100644 --- a/FeatureTest.md +++ b/FeatureTest.md @@ -8,4 +8,4 @@ Feature tests will be available from WebAssembly itself, as well as from JavaScript. Details -[are still be hashed out](https://github.com/WebAssembly/spec/issues/90). +[are still be hashed out](https://github.com/WebAssembly/design/issues/90). |