Think about using mingw-w64 with dwarf exception support for rustc cross-compilation for 32bit Windows
Our workaround we currently use to cope with issues cross-compiling rustc for 32bit Windows is not upstreamable (see: https://github.com/rust-lang/rust/pull/55444 for the arguments). We could think about compiling with a mingw-w64 using dwarf exception support instead, see: (https://github.com/rust-embedded/cross/blob/master/docker/mingw.sh).
However, we should take into account that we want to switch to a mingw-w64/clang-based toolchain soon and should start looking into this ticket not before the other (#28238 (moved)) is done.
Activity
Trac:
Description: Our workaround we currently use to cope with issues cross-compiling rustc for 32bit Windows us not upstreamable (see: https://github.com/rust-lang/rust/pull/55444 for the arguments). We could think about compiling with a mingw-w64 using dwarf exception support instead, see: (https://github.com/rust-embedded/cross/blob/master/docker/mingw.sh).However, we should take into account that we want to switch to a mingw-w64/clang-based toolchain soon and should start looking into this ticket not before the other (#28238 (moved)) is done.
to
Our workaround we currently use to cope with issues cross-compiling rustc for 32bit Windows is not upstreamable (see: https://github.com/rust-lang/rust/pull/55444 for the arguments). We could think about compiling with a mingw-w64 using dwarf exception support instead, see: (https://github.com/rust-embedded/cross/blob/master/docker/mingw.sh).
However, we should take into account that we want to switch to a mingw-w64/clang-based toolchain soon and should start looking into this ticket not before the other (#28238 (moved)) is done.
-
Replying to tom:
Hm. I know that mingw-clang-x86 needs sjlj-exceptions because the default SEH exceptions are not supported there. But I'm confused why Tor needs a special case and the Mozilla builds don't.
What do you mean with special case? I doubt you are cross-compiling Rust for 32bit Windows. But we do mainly to be able to react "quickly" to potential reproducibility issues (see the infamous #26475 (moved) where this stance has helped).
Replying to gk:
Replying to tom:
Hm. I know that mingw-clang-x86 needs sjlj-exceptions because the default SEH exceptions are not supported there. But I'm confused why Tor needs a special case and the Mozilla builds don't.
What do you mean with special case? I doubt you are cross-compiling Rust for 32bit Windows. But we do mainly to be able to react "quickly" to potential reproducibility issues (see the infamous #26475 (moved) where this stance has helped).
Right; we're not, we download pre-compiled stuff (and repack it).
So I guess the answer is you need a patch to your version because you're compiling with a different compiler than us. (Presumably, the windows rust components are compiled using clang-cl or msvc on Windows?)
-
Replying to tom:
Replying to gk:
Replying to tom:
Hm. I know that mingw-clang-x86 needs sjlj-exceptions because the default SEH exceptions are not supported there. But I'm confused why Tor needs a special case and the Mozilla builds don't.
What do you mean with special case? I doubt you are cross-compiling Rust for 32bit Windows. But we do mainly to be able to react "quickly" to potential reproducibility issues (see the infamous #26475 (moved) where this stance has helped).
Right; we're not, we download pre-compiled stuff (and repack it).
So I guess the answer is you need a patch to your version because you're compiling with a different compiler than us. (Presumably, the windows rust components are compiled using clang-cl or msvc on Windows?)
Yes.