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 08:40:47 +0000 [thread overview]
Message-ID: <bug-115643-4-ywrKJsE5Dq@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 #15 from cqwrteur <unlvsur at live dot com> ---
(In reply to Evgeny Karpov from comment #13)
> Could you please confirm that the patch resolves the issue?
People like you need to be fired
next prev parent reply other threads:[~2024-06-28 8:40 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 [this message]
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
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-ywrKJsE5Dq@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: link
Be 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).