From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7D4FB3858025; Mon, 21 Aug 2023 12:44:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D4FB3858025 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1692621868; bh=YxRd/rV+W0c8sA9ZDK++7Ga4kl/7iXWo/j9UlF/plzs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=n7hxQ/AdBQIh1P/PnvnjmmpIofcwbOsAMcH3rZh4HElcbuTbbsrnlFu3jGEpKwNDa JXhqJUNm89SzZ28HQqFF77ljWMytMwL6VpYltFf6VrkCm52SuELGisfBjHhk7DN+Vh PbpW3BTGy2Lzms6kIds81//nGbpIWjNWZUG/ZhhU= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/111067] g++.dg/opt/icf{1,2,3}.C tests fail on darwin Date: Mon, 21 Aug 2023 12:44:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: iains 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: 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=3D111067 Iain Sandoe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iains at gcc dot gnu.org --- Comment #3 from Iain Sandoe --- I took a brief look at this over the weekend, but I need to check what is allowed/expected by the ABI - we normally reject cases where two externally-visible symbols have the same address, since that breaks the ld64 'atom model'; how to reconcile that constraint with 'no unique address' is interesting.=20=20 We do support merging literals, and we can support aliased symbols by instruction to the linker that they are - so there might be viable way(s) to implement.=