| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
Redirected a link on ES6 module integration to the future features page.
|
| |
|
|
| |
Now tracked by: #1087
As discussed here: #1066
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Require import/export names to be UTF-8.
This implements the UTF-8 proposal described in
https://github.com/WebAssembly/design/issues/989#issuecomment-284757788.
This does not currently rename "name" to "utf8-name", because if UTF-8 is
required for import/export names, there's a greater appeal to just saying
that all strings are UTF-8, though this is debatable.
* s/utf8/UTF-8/g
* Say "UTF-8 byte sequence" rather than "UTF-8 string".
This document is describing the encoded bytes, rather than the string which
one gets from decoding them.
Also, make the descriptions of the byte sequence length fields more precise.
* Fix typo.
|
| |
|
|
|
|
|
|
| |
* Export name uniqueness
spec test exports.wast makes it a validation failure for exported names to be duplicate. I find this somewhat surprising (I see exports as a dictionary, so duplicates simply overwrite previous entries), I'd therefore be happy if others want to reverse the polarity of this (make it OK to duplicate export names).
* Fix unintended change
|
| | |
|
| |
|
|
|
|
|
|
| |
* Start function clarifications
Resolves #896.
* Clarify
|
| |
|
|
|
|
|
|
| |
* Function index space is used by exports
* Mention start function as well
* Elements
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Clarify names section indexing
* Fix broken link
* Link start-section to Modules.md#function-index-space link
* Explicate index spaces
* Periods
|
| |
|
| |
Added brief item on multiple return.
|
| |
|
|
| |
(#837)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename AstSemantics.md to Semantics.md
* Rewrite Semantics for structured stack machine
* Update control instructions
* Update nop
* More tweaks
* Update README.md
* Update Semantics.md
* Update Semantics.md
* Address @rossberg-chromium comments
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Clarify that wasm may be viewed as either an AST or a stack machine. (#686)
* Clarify that wasm may be viewed as either an AST or a stack machine.
* Reword the introductory paragraph.
* Add parens, remove "typed".
* Make opcode 0x00 `unreachable`. (#684)
Make opcode 0x00 `unreachable`, and move `nop` to a non-zero opcode.
All-zeros is one of the more common patterns of corrupted data. This
change makes it more likely that code that is accidentally zeroed, in
whole or in part, will be noticed when executed rather than silently
running through a nop slide.
Obviously, this doesn't matter when an opcode table is present, but
if there is a default opcode table, it would presumably use the
opcodes defined here.
* BinaryEncoding.md changes implied by #682
* Fix thinko in import section
* Rename definition_kind to external_kind for precision
* Rename resizable_definition to resizable_limits
* Add opcode delimiter to init_expr
* Add Elem section to ToC and move it before Data section to reflect Table going before Memory
* Add missing init_expr to global variables and undo the grouped representation of globals
* Note that only immutable globals can be exported
* Change the other 'mutability' flag to 'varuint1'
* Give 'anyfunc' its own opcode
* Add note about immutable global import requirement
* Remove explicit 'default' flag; make memory/table default by default
* Change (get|set)_global opcodes
* Add end opcode to functions
* Use section codes instead of section names
(rebasing onto 0xC instead of master)
This PR proposes uses section codes for known sections, which is more compact and easier to check in a decoder.
It allows for user-defined sections that have string names to be encoded in the same manner as before.
The scheme of using negative numbers proposed here also has the advantage of allowing a single decoder to accept the old (0xB) format and the new (0xC) format for the time being.
* Use LEB for br_table (#738)
* Describe operand order of call_indirect (#758)
* Remove arities from call/return (#748)
* Limit varint sizes in Binary Encoding. (#764)
* Global section (#771)
global-variable was a broken anchor and the type of count was an undefined reference and inconsistent with all the rest of the sections.
* Make name section a user-string section.
* Update BinaryEncoding.md
* Update BinaryEncoding.md
* Use positive section code byte
* Remove specification of name strings for unknown sections
* Update BinaryEncoding.md
* Remove repetition in definition of var(u)int types (#768)
* Fix typo (#781)
* Move the element section before the code section (#779)
* Binary format identifier is out of date (#785)
* Update BinaryEncoding.md to reflect the ml-proto encoding of the memory and table sections. (#800)
* Add string back
* Block signatures (#765)
* Replace branch arities with block and if signatures.
Moving arities to blocks has the nice property of giving implementations
useful information up front, however some anticipated uses of this
information would really want to know the types up front too.
This patch proposes replacing block arities with function signature indices,
which would provide full type information about a block up front.
* Remove the arity operand from br_table too.
* Remove mentions of "arguments".
* Make string part of the payload
* Remove references to post-order AST in BinaryEncoding.md (#801)
* Simplify loop by removing its exit label.
This removes loop's bottom label.
* Move description of `return` to correct column (#804)
* type correction and missing close quote (#805)
* Remove more references to AST (#806)
* Remove reference to AST in JS.md
Remove a reference to AST in JS.md. Note that the ml-proto spec still uses the name `Ast.Module` and has files named `ast.ml`, etc, so leaving those references intact for now.
* Use "instruction" instead of "AST operator"
* Update rationale for stack machine
* Update Rationale.md
* Update discussion of expression trees
* Update MVP.md
* Update Rationale.md
* Update Rationale.md
* Remove references to expressions
* Update Rationale.md
* Update Rationale.md
* Address review comments
* Address review comments
* Address review comments
* Delete h
|
| |
|
|
|
|
|
|
| |
* Move segment and start operations to the end
* Add link to Assert
* Fix grammar, add imported Tables link
|
| |
|
|
|
| |
This is renamed to "anyfunc" in AstSemantics.md in #682.
Also, fix grammar in the Elements Section.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add Memory, Table and multi-import/export of these
* Clarify mutation of elements
* Mention CFI use case
* Clarify call_table signature mismatches
* Explicate elements section
* Change support to allow/enable
* Remove table/memory indices add global imports/exports
* Clarify host-defined (i.e., JavaScript) table elements
* s/necessary/useful
* s/will/may/
* Fix typo
* Fix typo
* Clarify that table updates are observed by all instances
* Clarify that host-defined table element values can have different signature checking
* Just 'constraints' since more detail is below
* Wordsmith DynamicLinking.md intro
* Wordsmith FutureFeatures.md
* Try to clarify wording in FutureFeatures.md
* Change 'function' to 'anyfunc'
* Fix nits
* Refine description of initializer expressions
* Remove the Definition Index Space, use (type, index) pairs as necessary
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
statement.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Fix up some references about dynamic linking and move it to its own file, since
it will be expanding soon and referring to a fair number of other sections.
Also add a little extra motivation to the introductory text.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
