Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Float32 #32

Merged
merged 3 commits into from
Aug 28, 2015
Merged

Float32 #32

merged 3 commits into from
Aug 28, 2015

Conversation

rossberg
Copy link
Member

Merged to the wrong branch before

rossberg added a commit that referenced this pull request Aug 28, 2015
@rossberg rossberg merged commit c0b5385 into master Aug 28, 2015
@rossberg rossberg deleted the float32 branch August 28, 2015 03:06
littledan pushed a commit to littledan/spec that referenced this pull request Mar 4, 2018
See comments in WebAssembly#24:

* Throw an error when constructing shared memory without maximum.
* Lazily create a new SharedArrayBuffer and freeze it after grow.
eqrion pushed a commit to eqrion/wasm-spec that referenced this pull request Jul 18, 2019
I recently looked into adding support for bulk memory operations into
some Rust tooling in preparation for an overall threading story, and on
reading the overview here I was slightly confused about a few encodings
and some semantics. In the end I'm hopeful that these updates can help
clarify these for future readers! No major functional change is intended
here, only tweaks to wording and clarification of what I believe the
original intent of the instructions were.

Changes made were:

* Fixed a broken `modules.html` link
* Clarified some wording about how the new encoding of data segments
  with a flags field up front is backwards compatible.
* Lifted the style of specifying encodings in `BinaryEncoding.md` to
  replace the current table for the new encoding of a data section. (I
  found this to be a bit more readable, but it should be functionally
  the same!)
* Update `memory.*` instructions (and transitively `table.*`) to all be
  succeeded by an immediate index of which memory/table to operate over.
  This should, in the future, allow initializing/dropping data segments
  with multiple memories in play.
* Updated the chart of instruction binary encodings to explicitly
  specify the following immediates of segments and tables.
dhil added a commit to dhil/webassembly-spec that referenced this pull request Apr 29, 2024
Merge with upstream/`wasm-3.0+exn`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant