Skip to content

Put f32.const before f64.const, for consistency. #696

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

Closed
wants to merge 3 commits into from

Conversation

sunfishcode
Copy link
Member

This is for the binary_0xc branch, and is one step of a broader opcode reorganization.

…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`, 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.
@kripken
Copy link
Member

kripken commented May 23, 2016

lgtm

@rossberg
Copy link
Member

I'm fine with all the changes you have suggested so far. But instead of making many tiny changes individually, how about a single comprehensive PR for reorganising the opcode space? That would help seeing the big picture and not fragmenting the discussion.

@titzer
Copy link

titzer commented Aug 1, 2016

Shall we do this in 0xD?

@rossberg
Copy link
Member

Should be subsumed by #826 now.

@jfbastien jfbastien closed this Oct 31, 2016
@sunfishcode sunfishcode deleted the f32-f64 branch November 22, 2016 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants