-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
system_v <-> windows_fastcall mixup #146
Comments
Build from 1c0efd0. |
Same problem with 2b5be77 (master) |
This is on Linux, so I have no idea how it tried to use |
When run that wasm module, I get:
so something odd is going on. |
I can confirm that I'm getting the same error as @sunfishcode. |
I don't know how related that is, however, I have cloned your repo bjorn3/rust/tree/compile_rustc_for_wasm, I've built it, and managed to run it and print In order to compile
And got the expected output:
Note that I've used the release version of wasmtime. Also, when simply running
I stumbled upon the following
The |
After recompiling wasmtime from scratch it seems to work. |
We have only ever used Unknown for the stdio streams, and I don't expect us to use it for anything else in the future, so rename it. Set the returned filetype to character device: Closes bytecodealliance#146. Also, fix some warnings.
This patch rebrands a few public APIs from typed-continuations to stack-switching. Resolves bytecodealliance#146.
Add support for fetching models containing unspecified values. With the addition of declared sorts in bytecodealliance#141, this broke the code that parses constants from SMT models. The backend solvers differ on how they implement this. This PR deals with the CVC5 format only, in which unspecified values are represented as something like `(as @Unspecified_0 Unspecified)`. Updates avanhatt#45
The text was updated successfully, but these errors were encountered: