From e2be77eaac770268a4c22fb09c6f648de7b9b6b8 Mon Sep 17 00:00:00 2001 From: Joseph Richey Date: Wed, 15 Nov 2017 08:48:14 -0800 Subject: Fixup links to future features (#1157) This link standardizes how all the other design pages will refer to future features (either in `FutureFeatures.md` or in a tracking issue). All links to these upcoming features now use references at the bottom of the doc page (as opposed to inline links or references). Note that this change makes it very easy for the doc links to be updated when a tracking issue is started. As all the references have a standard format; a simple find/replace script will get everything. This commit also makes sure that references now point to a tracking issue if one exists. Note that this means a future CL can now delete some of the unnecessary sections from `FutureFeatures.md`. The only visible change from this commit is that certain broken links are now fixed, or links pointing to a doc section now point to the correct tracking issue. --- Security.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'Security.md') diff --git a/Security.md b/Security.md index 4f81c18..656b85a 100644 --- a/Security.md +++ b/Security.md @@ -58,13 +58,13 @@ compile time. This is an isolated memory region with fixed maximum size that is zero initialized by default. References to this memory are computed with infinite precision to avoid wrapping and simplify bounds checking. In the future, support for [multiple linear memory sections](Modules.md#linear-memory-section) and -[finer-grained memory operations](FutureFeatures.md#finer-grained-control-over-memory) +[finer-grained memory operations][future memory control] (e.g. shared memory, page protection, large pages, etc.) will be implemented. [Traps](Semantics.md#traps) are used to immediately terminate execution and signal abnormal behavior to the execution environment. In a browser, this is represented as a JavaScript exception. Support for -[module-defined trap handlers](FutureFeatures.md#trappingor-non-trapping-strategies) +[module-defined trap handlers][future trapping] will be implemented in the future. Operations that can trap include: * specifying an invalid index in any index space, @@ -180,4 +180,6 @@ in WebAssembly. [stack smashing protection]: https://en.wikipedia.org/wiki/Buffer_overflow_protection#Random_canaries [time of check to time of use]: https://en.wikipedia.org/wiki/Time_of_check_to_time_of_use -[future threads]: FutureFeatures.md#threads +[future threads]: https://github.com/WebAssembly/design/issues/1073 +[future memory control]: FutureFeatures.md#finer-grained-control-over-memory +[future trapping]: FutureFeatures.md#trapping-or-non-trapping-strategies -- cgit v1.2.3