You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 3, 2024. It is now read-only.
I've been investigating getting threads working with Rust and wasm32-unknown-emscripten, and I came across a previous message of yours which make it seem like threads were working at one time. When I try your example program, I get errors seemingly related to thread local storage like:
...relocation R_WASM_MEMORY_ADDR_TLS_SLEB cannot be used against non-TLS symbol `std::io::stdio::OUTPUT_CAPTURE::__getit::__KEY::h776cf75763f0fad1`
...can you confirm that threading was working at one time, and there must have been a regression somewhere between now and then? I've tried with emscripten v3.0.0, and one prior version with the same wasm-ld error.
Thanks!
The text was updated successfully, but these errors were encountered:
No, what I meant by that comment is that I created a reproduction repo that demonstrates the linking issues (that is, it was broken from the beginning).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
I've been investigating getting threads working with Rust and wasm32-unknown-emscripten, and I came across a previous message of yours which make it seem like threads were working at one time. When I try your example program, I get errors seemingly related to thread local storage like:
...can you confirm that threading was working at one time, and there must have been a regression somewhere between now and then? I've tried with emscripten v3.0.0, and one prior version with the same
wasm-ld
error.Thanks!
The text was updated successfully, but these errors were encountered: