bjorn3

@tamme @HenrikLievonen I'm not aware of that failure mode. Is it cargo or rustc that uses the wrong path? Windows, macOS or Linux? If a unix, does your system locale use UTF-8 or not?

@sunfish@hachyderm.io You might want to do deterministic replay for record-replay debugging. Or you might want to record the random numbers used to derive a TLS encryption key to make wireshark work. Or you might want to get a bunch of random numbers once and then run the same computation using those random numbers on multiple systems to check they match. All of these can be done by virtualizing the random-number generator, but require wasm runtime integration if random numbers were part of the component model. Edit: and to add none of these match the secure vs on-secure rng distinction. for all of them you do actually want to virtualize the secure rng too.

@jsbarretto@social.coop @imperio@toot.cat @veloren@floss.social Cranelift, right? I don't recall doing that with GCC.

@jsbarretto@social.coop @imperio@toot.cat @veloren@floss.social Found it by the way: https://github.com/rust-lang/rustc_codegen_cranelift/issues/1412 + some conversation on the veloren discord.

@HenrikLievonen @laund @tamme Maybe having rustc set LC_MESSAGES=C instead of LC_ALL=C would work?

@esoterra@hachyderm.io @sunfish@hachyderm.io I think such a check would fit better in the tools used to compose the wasm component.