public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org 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 Date: Fri, 28 Jun 2024 09:34:41 +0000 [thread overview] Message-ID: <bug-115643-4-FJDFwIqsRg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115643-4@http.gcc.gnu.org/bugzilla/> 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-bugzilla@gcc.gnu.org> Sent: Friday, June 28, 2024 5:19:03 AM To: unlvsur@live.com <unlvsur@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.
next prev parent reply other threads:[~2024-06-28 9:34 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com 2024-06-25 12:57 ` [Bug target/115643] " unlvsur at live dot com 2024-06-25 19:36 ` Evgeny.Karpov at microsoft dot com 2024-06-26 14:15 ` slyfox at gcc dot gnu.org 2024-06-26 14:22 ` slyfox at gcc dot gnu.org 2024-06-26 20:18 ` slyfox at gcc dot gnu.org 2024-06-26 20:20 ` slyfox at gcc dot gnu.org 2024-06-26 20:38 ` Evgeny.Karpov at microsoft dot com 2024-06-26 20:57 ` ubizjak at gmail dot com 2024-06-26 21:09 ` Evgeny.Karpov at microsoft dot com 2024-06-26 21:52 ` unlvsur at live dot com 2024-06-26 21:52 ` unlvsur at live dot com 2024-06-27 2:08 ` [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 sjames at gcc dot gnu.org 2024-06-27 3:56 ` pinskia at gcc dot gnu.org 2024-06-27 7:25 ` Evgeny.Karpov at microsoft dot com 2024-06-28 8:39 ` Evgeny.Karpov at microsoft dot com 2024-06-28 8:40 ` unlvsur at live dot com 2024-06-28 8:40 ` unlvsur at live dot com 2024-06-28 8:45 ` unlvsur at live dot com 2024-06-28 8:49 ` unlvsur at live dot com 2024-06-28 9:07 ` slyfox at gcc dot gnu.org 2024-06-28 9:13 ` unlvsur at live dot com 2024-06-28 9:19 ` redi at gcc dot gnu.org 2024-06-28 9:34 ` unlvsur at live dot com [this message] 2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org 2024-06-28 12:51 ` clyon at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-115643-4-FJDFwIqsRg@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).