Mateusz Mikuła

Also happens for me on Windows 11 using PolyMC 1.4.2.

Thank you! I have not scrolled low enough to find them previously 🤦🏻‍♂️

> While at it, replace the very sad, sad, grammatically-incorrect one-liner of a commit message with a detailed explanation of the context, the intent and the justification of the code...

Oh sorry, I was under impression you intended to change in-code comment.

Yeah, I have misunderstood the intention.

We have fixed some of unwinding issues, does this still reproduce?

I hacked source code (by disabling what fails to build) and it passed the build but the compiler is totally broken.

I've tried aborting instead of unwinding but this doesn't help. Seems we need proper unwinding because code that runs proc-macros relies on catching the exceptions. What I believe the issue...

There is some oddity in `llvm-nm`: ``` $ /clang64/bin/nm /d/tmp/r/src/CLANG32/build/i686-pc-windows-gnu/stage1/lib/rustlib/i686-pc-windows-gnu/lib/rsbegin.o | grep eh_frame 00000000 R __ZN7rsbegin9eh_frames10mingw_init6P_INIT17hcac2d6c918db7f49E 00000000 R __ZN7rsbegin9eh_frames10mingw_init8P_UNINIT17h565e94d416ee6b01E 00000000 b __ZN7rsbegin9eh_frames3OBJ17hc37ee6dbaafc1617E 00000000 T __ZN7rsbegin9eh_frames4init17h9df17b84a7f77d8bE 00000030 T __ZN7rsbegin9eh_frames6uninit17h82158f3bb655b85bE 00000004 D...

FWIW Rust has it's own CRT begin and end files: https://github.com/rust-lang/rust/tree/master/library/rtstartup and does not use those from C toolchain.