Mateusz Mikuła

Reproduces with few hours old trunk: ``` $ /e/tmp/install/bin/clang "-cc1" "-triple" "aarch64-w64-windows-gnu" "-emit-obj" "--mrelax-relocations" "-disable-free" "-clear-ast-before-backend" "-disable-llvm-verifier" "-discard-value-names" "-main-file-name" "dtrsm_kernel_LN.c" "-mrelocation-model" "pic" "-pic-level" "2" "-mframe-pointer=none" "-fmath-errno" "-ffp-contract=on" "-fno-rounding-math" "-mconstructor-aliases" "-mms-bitfields"...

In build with assertions enabled one of them has fired: ``` $ /e/tmp/build/bin/clang "-cc1" "-triple" "aarch64-w64-windows-gnu" "-emit-obj" "--mrelax-relocations" "-disable-free" "-clear-ast-before-backend" "-disable-llvm-verifier" "-discard-value-names" "-main-file-name" "dtrsm_kernel_LN.c" "-mrelocation-model" "pic" "-pic-level" "2" "-mframe-pointer=none" "-fmath-errno"...

And update to LLVM 15.0.1 while at it.

After applying this diff on Clang subsystem it went further: ```diff $ diff -u zig/lib/std/target.zig zig/lib/std/target1.zig --- zig/lib/std/target.zig 2022-10-22 14:37:45.101840400 +0200 +++ zig/lib/std/target1.zig 2022-10-22 13:38:49.160000000 +0200 @@ -1432,6 +1432,8 @@...

Is sacrificing some debugging possibilities worth 0.3% size decrease in case of GCC? ```bash $ nm /clang64/bin/python.exe | wc -l 166 $ cp /clang64/bin/python.exe . $ strip --strip-all python.exe $...

It can be used to quickly tell whether some features of other libraries (like jit, specific compression formats) are enabled (or at least linked). It's not a huge deal for...

> > understandable not even sure if our port works with later versions of gcc as development on dragonegg halted around gcc-4.8... strangely gcc-9 had working plugin support but later...

For UNIX (and therefore Cygwin/MSYS2) leading `/` means root directory so to call `cl` inside MSYS2 you have to replace them with `-` so your command becomes: `cl -nologo -w...

Possibly due to repo move GitHub ignores pushes to this branch, moving to new PR: https://github.com/rust-lang/cc-rs/pull/734

It's not easy to obtain them: we would have to build them ourselves. Also there are issues like https://github.com/rust-lang/rust/issues/88704 that have been fixed in recent GCC versions (it shouldn't appear...