From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A315B3833EA2; Fri, 16 Dec 2022 18:35:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A315B3833EA2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1671215752; bh=wHDWZX8Tnbrrv/jG48kHaGwqHpFOSxneqX6bE5PcAv4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ay0nf9ynzE8A15H4qL+JpxgVtVWyvz/lRMClfgYqLIZSokQUzSGa425FmMCkr3XhS 2IKk5qstn7LX00k1TpXiCthOGX2ZwVx2kr4+lAUL1mVgPGhOk36n0mDguYM1SSMmWX 11yDNSrWjGBmW38e237I9w4Gf380lM4KsW/VZlng= From: "tschwinge at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rust/108113] Rust and --enable-link-serialization=1 Date: Fri, 16 Dec 2022 18:35:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rust X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tschwinge at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dkm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D108113 Thomas Schwinge changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tschwinge at gcc dot gnu.o= rg --- Comment #2 from Thomas Schwinge --- Marc, given Jakub's approval in , are = you going to push "rust: fix link serialization [PR108113]" to GCC upstream mas= ter branch, too? --- There's no reason, in opinion, to block such ongoing development/fixes on t= he GCC/Rust backlog upstreaming process.=