Nothing useful, just an obscure bug with an obscure kinda compiler. Works perfectly on Arch but not on Fedora.
18:52 relative@fedora-pc /home/relative/Coding/wtest
% winegcc --version
[1] 25170 segmentation fault (core dumped) winegcc --version
Core dump:
PID: 8632 (winegcc)
UID: 1000 (relative)
GID: 1000 (relative)
Signal: 11 (SEGV)
Timestamp: Fri 2025-06-20 18:21:40 MSK (27min ago)
Command Line: winegcc
Executable: /usr/bin/winegcc
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-Alacritty@39e91e26a9de44799b2de26>
Unit: user@1000.service
User Unit: app-Alacritty@39e91e26a9de44799b2de2678cfdb02c.service
Slice: user-1000.slice
Owner UID: 1000 (relative)
Boot ID: 3f9a7e93b4294e198d0b781c4ca4665c
Machine ID: e38a5023bf1240be8b315114c6f66875
Hostname: fedora-pc
Storage: /var/lib/systemd/coredump/core.winegcc.1000.3f9a7e93b4294e198d0b781c4ca4665c.8632.17504329000>
Size on Disk: 23.2K
Message: Process 8632 (winegcc) of user 1000 dumped core.
Stack trace of thread 8632:
#0 0x00007fa46c1901dd __strlen_avx2 (libc.so.6 + 0x1491dd)
#1 0x00000000004040d8 strendswith (/usr/bin/winegcc + 0x40d8)
#2 0x0000000000400db7 main (/usr/bin/winegcc + 0xdb7)
#3 0x00007fa46c04a5f5 __libc_start_call_main (libc.so.6 + 0x35f5)
#4 0x00007fa46c04a6a8 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x36a8)
#5 0x0000000000403ff5 _start (/usr/bin/winegcc + 0x3ff5)
ELF object binary architecture: AMD x86-64
PID: 9339 (winegcc)
UID: 1000 (relative)
GID: 1000 (relative)
Signal: 11 (SEGV)