From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 11D493875431; Wed, 26 Jun 2024 21:52:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11D493875431 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1719438740; bh=2Y/l7cfvN3yw6SB87aLrqyCmmjAr4RcrKzShFBifM7Y=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mSbY8KZQOi4QbQh4L4kzaATi3jZQsKdcMVIwDZ+sU3CpA/ZLlPI7STW8Cd+/ekM7Y QdUkAjBwkKtV/lvxIvpniYODBGas2mFukZXdMRg2OBsOJZnW0bjZaApy2c/N51FmAh aMqDbdfCfir8irFLHtJMXU4hwqbcs17hHv1RG3Dc= From: "unlvsur at live dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 Date: Wed, 26 Jun 2024 21:52:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: unlvsur at live dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115643 --- Comment #10 from cqwrteur --- (In reply to Evgeny Karpov from comment #9) > Sure, it will be included in the patch. What's the progression of GCC for aarch64-windows-gnu? How long would it be done? I want to buy a surface pro 11 to use it.=