@WG-prioritization/alerts issue #76984 has been requested for prioritization.
How frequently used is this toolchain? If someone else can repro it and the toolchain is fairly often used then this should be critical.
If the bug report is right, I don’t see how CI didn’t catch this.
I assume we only test MSVC on Windows.
I'm pretty sure we test GNU but you could ask in #t-infra
I suspect we have some dependency installed in the CI builder that doesn't come with mingw by default
x86_64-pc-windows-gnu target (with MinGW) is listed as tier 1 ("guaranteed to work"), so it should have passed tests
I‘m assuming we have a test for an empty main. 😅
It’s sleeping time here, so I’ll run a bisection tomorrow Morning (if someone hasn’t done it by then).
I tried reproducing the issue, but wasn't able to. Haven't used Rust in Windows previously (only inside WSL), so it was a clean install of MinGW-w64. Tried on stable, latest nightly (
2020-09-19) and the nightly mentioned in the issue that was supposed to be broken (
2020-09-09). All three build fine for me, so I'm not sure exactly where the issue is.
Hmm, tried a bit more and I was able to reproduce by replacing the gcc installation I had (Mingw-w64 install from Msys2) with the one mentioned in the issue (TDM-GCC). So it might be an issue with that specific compiler?
Yeah, sounds like we can close this then. We only support what we ship/test with/document, so not TDM-GCC.
do someone want to proceed and close this one then?, don't have a lot of context myself
Don't have enough context, too, but it looks like is can be safely closed. I'll close it myself if there are no further comments to investigate the issue (which of course can be always be re-opened)
should we remove
I-prioritize from this issue?
I think we should give it P-low - it looks like there's a bug here but for an unsupported toolchain
I'd be for close, because... Well... We don't want too many "unsupported" issues littering the tracker.
@Joshua Nelson Does that sound good?
unless people show up for helping fixing the issue, closing makes sense to me.
Issue #76984's prioritization request has been removed.