| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Otherwise, it would not be possible for engines to look up the offset
with O(1) complexity because `count` would have a variable length.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This commit introduces third-party extensions to the MVP, branded as
"NanoWasm", that aim to reduce memory consumption and computational time
for resource-constrained environments, at the expense of increased
module file size.
|
| |
|
| |
To keep any existing links valid, redirect to the new canonical code of conduct rather than deleting this file.
|
| |
|
| |
Clarify description of function_body length field.
|
| |
|
| |
Fixes #1487
|
| |
|
|
|
| |
- Clarify language when talking about LLVM
- Correct "but which can..." to "but can..."
- "...this issue at point" to "this issue at some point"
|
| |
|
|
|
|
|
| |
* Add details of disciplinary action to CoC
Co-authored-by: Thomas Lively <7121787+tlively@users.noreply.github.com>
Co-authored-by: Nick Fitzgerald <fitzgen@gmail.com>
Co-authored-by: Derek Schuff <dschuff@chromium.org>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* Update FutureFeatures.md
This table has become out-of-date, and I don't believe we're planning to keep in in sync with the proposals repo. The linked tracking issues are also out-of-sync with the actual proposal statuses, since we've moved away from using them in general.
Prompted by https://github.com/WebAssembly/design/issues/1370
* Update FutureFeatures.md
|
| |
|
| |
I think these were intended to be `h2`s :)
|
| |
|
|
|
| |
* Now we have IEEE 754-2019 instead of IEEE 754-2008
* Add 64bit version for additional integer operators
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Define non-trapping float-to-int conversions.
This also introduces the concept of prefix bytes, and defines the "numeric" prefix
byte, used for encodin the new conversion instructions.
* Add feature markers.
* Add the feature marker in more places.
* Rename "numeric" to "misc".
See https://github.com/WebAssembly/nontrapping-float-to-int-conversions/issues/5.
* Rename opcodes.
See https://github.com/WebAssembly/spec/issues/884#issuecomment-426433329.
|
| |
|
| |
Existing link (https://jsmodules.io) is broken. Can be replaced with this MDN link?
|
| |
|
|
| |
Discussions of wasm64 have settled on thinking of it as a per-memory flag,
rather than a per-module flag, so update this documentation accordingly.
|
| |
|
|
|
|
| |
* Fix broken links to GC.md
* Update links to proposals repo
|
| | |
|
| |
|
| |
Updating SIMD proposal phase
|
| |
|
| |
Thanks!
|
| |
|
|
|
| |
In my attempt to link to the official LLVM repo, a mistake was made in
the new URL (I wrongly assumed the old mirror and the official mono-repo
has the same structure). This should fix that mistake.
|
| |
|
|
| |
LLVM has an official repository on Github now. Link to it instead of the mirror
repo.
|
| |
|
| |
See issue #1258.
|
| | |
|
| |
|
|
|
| |
These two anchor links were referencing the wrong URL.
Updated `#datatype-conversions` to `#datatype-conversions-truncations-reinterpretations-promotions-and-demotions`
|
| |
|
|
|
| |
This link was not resolving correctly.
Changed `#control-flow-structures` to `#control-constructs-and-instructions`
|
| | |
|
| |
|
| |
See https://github.com/WebAssembly/design/issues/1217
|
| |
|
| |
Sign-extension operators and non-trapping float-to-int conversions are both at the "Standardize the Feature" phase.
|
| | |
|
| |
|
|
|
|
| |
All the modified URLs were checked to see if they are available over
HTTPS by opening a new tab in the browser, entering the URL in the
address bar, changing http:// to https:// and then verifying if the
resource displayed is the same over HTTP and HTTPS for each URL.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
The Sign-extension operators and Import/Export Mutable Globals proposals were moved to the implementation phase in the Feb 6th CG meeting.
|
| | |
|
| |
|
|
|
| |
It hasn't been maintained and was last touched 3 years ago. It's misleading to keep here, and there were aspirations that whatever tools maintain webassembly.org would do this instead.
Addresses #1176
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Delete unnecessary sections
As garbage collection, multiple return, and Memset/Memcpy Operators have
dedicated tracking issues and all the links have been fixed, we can
remove their sections. Most of the data being removed is still present
in the tracking issues.
The two sections on tail calls are not removed as they contain some
information not in the tail calls tracking issue (#1144).
* Create section for preserving old links
This commit creates a section containing all proposals moved to tacking
issues. It also does some general cleanup.
|
| |
|
|
|
| |
Both links to the CAndC++.md file are broken (when viewing the documents
on github.com). This commit fixes the markdown links by escaping the "+"
symbols.
|
| |
|
|
| |
PR #1065 removed the referenced documenation on streaming compilation.
This commit just removes the reference and surrounding paragraph.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
| |
Add phases, some issues were missing.
|
| | |
|
