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.

Sign up for GitHub

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

Jump to bottom

multiple build processes, processes disagree #59

Closed
sunfishcode opened this issue Sep 14, 2015 · 3 comments · Fixed by #92
Closed

multiple build processes, processes disagree #59

sunfishcode opened this issue Sep 14, 2015 · 3 comments · Fixed by #92

Comments

@sunfishcode
Copy link
Member

When using src/Makefile, one gets an executable at src/wasm. However, runtests.py expects an executable at src/main.native. It'd be useful for these to agree; which one is preferable?
@kg
Copy link
Contributor

kg commented Sep 14, 2015

Happy to update runtests to handle this. I personally dislike what ocamlbuild does.

@rossberg
Copy link
Member

SGTM as well. Would be nicer if we did get a binary named wasm in a consistent place (preferably outside the src dir). Can one do that with ocamlbuild?

@sunfishcode
Copy link
Member Author

It looks like #83 would fix this.

@sunfishcode sunfishcode mentioned this issue Sep 30, 2015
Merged
littledan pushed a commit to littledan/spec that referenced this issue Mar 4, 2018
@bnjbvr @binji
Fix inconsistency with wait timeout value in example (WebAssembly#59)
fae1e3a 
The spec says that wait's third argument is an i64, but the example shows a f64, probably following a previous version of the spec.
eqrion pushed a commit to eqrion/wasm-spec that referenced this issue Jul 18, 2019
@binji
[Interpreter] Decode/encode the data count section (WebAssembly#59)
5e3df28
alexcrichton pushed a commit to alexcrichton/spec that referenced this issue Nov 18, 2019
@dtig
Remove text about flushing of subnormals (WebAssembly#59)
81081fe 
Default to full IEEE 754 support for now. The issue of handling subnormals needs to be addressed (possibly by a global FTZ flag or mode switching), but allowing platforms to behave differently on FTZ semantics should not be baked into the specification.
alexcrichton pushed a commit to alexcrichton/spec that referenced this issue Nov 19, 2019
@lukewagner
Merge pull request WebAssembly#59 from WebAssembly/rename-again
684c69f 
Rewrite explainer (again) to take into account new names, scope, and concepts
dhil pushed a commit to dhil/webassembly-spec that referenced this issue Mar 2, 2023
@maxnordlund @aheejin
Fix syntax typo (WebAssembly#59)
32ad951
dhil pushed a commit to dhil/webassembly-spec that referenced this issue Mar 2, 2023
@titzer
Merge pull request WebAssembly#59 from WebAssembly/rm_let
9687d15 
Remove test cases with let
rossberg pushed a commit that referenced this issue Nov 6, 2024
@sbc100
Revert parameterization of limits that was added in #13. (#59)
6f101d6 
See WebAssembly/memory64#50 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix the path to the wasm executable to match what the Makefile builds. WebAssembly/spec
3 participants
@kg @rossberg @sunfishcode