Ryan Hunt

> There are only non-local transformations, and they are either very expensive (trampolining through exception handlers, like @fgmccabe is alluding to, provided you even have them) or only practical in...

I'd like to do this too. rust-bindgen has the same problem. Unfortunately - https://github.com/rust-lang/cargo/issues/1982

Was able to find a potential workaround here for the `cargo` issue. ``` [[bin]] name = "mybinary" path = "src/main.rs" required-features = ["binaries"] [dependencies] docopt = { version = "0.8.1",...

> * the "relaxed/non-deterministic" mode should be a clear default - I would personally be fine with relaxed SIMD phase 4 even before profiles are finalised (especially if we drop...

> similar to the way we'll need to make `memory.grow` always succeed/fail. Does the current deterministic profile also restrict these?

I agree that this is sort of a threads proposal issue, but it does affect the name we choose here so I think it's worth discussing so we don't paint...

@rossberg How do you feel about renaming the profile to `numeric-determinism` (or `numeric-deterministic`) then, as it won't encompass shared-memory determinism?

@rossberg My impression was that `numeric-determinism` would be useful for large cloud platforms that want to minimize architectural differences while still allowing multithreading. In the end, we'll probably want both...

As you said above, wasmtime has a canonicalize-nans option, which is the 1.0/2.0 version of numeric-determinism. So it's very much not hypothetical. Again, I'm fine if you want to start...

wasmtime has support for threading and the option is only to canonicalize-nans, it's not a full determinism option. I'm also not sure why you're saying there's no customer that would...