From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 967C23858D32; Wed, 6 Sep 2023 08:37:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 967C23858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693989425; bh=fjE4NYrXhp5HJ62ndBsMdNNgpkAgvpjzJ/y27+8a04g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RMtEWriKaWSbIhQgI7nlwVH7FtlTb8dIS65FupA00+5qC3RQSn02nNHOQRL/KBRt8 udRYyBOCkpmi3pL0tyXIpenmoWiLny7A5QN4Uz6ERRmc48TKIyh7k23RehSL9ugE/t HZboosK40csbtt0RvwQeF8FC2IeTlCx0kX+F2/3o= From: "clyon at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/111238] libstdc++ tests should use -Wl,-gc-sections in more configurations Date: Wed, 06 Sep 2023 08:37:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: clyon at gcc dot gnu.org X-Bugzilla-Status: NEW 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=3D111238 --- Comment #3 from Christophe Lyon --- The original problem is fixed by https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628998.html, and it s= eems better not to call GLIBCXX_CHECK_LINKER_FEATURES and silently hide a potent= ial problem. Maybe we should actually remove -gc-sections from native builds too, so that all configurations are consistent? https://gcc.gnu.org/pipermail/gcc-patches/2023-September/629031.html=