-
Notifications
You must be signed in to change notification settings - Fork 42
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
rustc.html example not working #30
Comments
@RealSput let's continue the discussion of rust-lang/miri#722 (comment) here. What do you see in the terminal window on the page itself? |
I see this error:
which is caused by: console.log(fds[5].dir.contents["hello.hello.7631c747841c2a99-cgu.0.rcgu.o"].data); And when I log |
That is in the dev tools console, right? What does the page itself show? |
Just xterm.js terminal. No links. |
And does the terminal show anything? |
It seems like rustc crashed early on or something. Can you also post a screenshot of the browser console? |
I'm getting a failure also, but with more info in the xterm console:
|
That panic is expected. It fails after writing the object files and before attempting to link. Linking doesn't work yet as there is no linker compiled for wasi. You should still see links to download the object files. |
Oh awesome. Is it possible to get it to output a .wasm file via the |
LLVM can't currently be compiled for wasm, so I used my cranelift based backend for codegen. Cranelift doesn't yet support compiling to wasm modules: bytecodealliance/wasmtime#2566 |
As of 9289c4c it is now able to reach the exact point where the linker would be invoked again, rather than panicking during linking preparation. I have also verified that it produces an object file and presents a download link for this. Compiling to wasm is tracked by bytecodealliance/wasmtime#2566. |
No description provided.
The text was updated successfully, but these errors were encountered: