https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643
--- Comment #21 from cqwrteur <unlvsur at live dot com> --- First, the bug is not caused by me and I am just reporting the issue here. Why should I waste my time to test for him? Second, I am tired of building compilers again and again just to fix a regression every day. My machine is super slow with no SSD. BTW do I even make a decision on whether a patch would get merged into GCC? Did you merge my patch on fixing libstdc++’s abi break? Oh it does not follow your “code standard” plus you hate me for that freestanding thing and I get it. Ok, then fix it yourself. Sorry, I am not going to do either of them. I am not going to test it and I am not going to fix the ABI bug. It is better you don’t fix the ABI regression and let the GNU/Linux die. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows ________________________________ From: redi at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> Sent: Friday, June 28, 2024 5:19:03 AM To: unlv...@live.com <unlv...@live.com> Subject: [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #20 from Jonathan Wakely <redi at gcc dot gnu.org> --- Your attitude and behaviour is not acceptable, as you've been told many times before. You will be banned if you continue. https://gcc.gnu.org/conduct.html -- You are receiving this mail because: You are on the CC list for the bug. You reported the bug.
