From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B552D3858D35; Thu, 29 Jun 2023 14:41:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B552D3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1688049696; bh=hdO0VMb30s4Ss3nBfeBIzfdYPScnQndYUYIvD5doQHg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=La/LVG0ilthvZ5NzvWIMv5Ytu+uB8L3dspicoQhINknSo7pk1ehAM/NALGxKEz//9 rBBz5DtOuLyXrKU5ianB1//3byPkhViu5+jS3QLLoXzTn6EU8HaEAkRcCxhw/QNKjc JAkUHBR7qNwRa5tZLz7efFLoGOtPkuRBLJfFMFcE= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris Date: Thu, 29 Jun 2023 14:41:36 +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: ABI X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D110077 --- Comment #10 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #9) > One solution would be to just add the declaration to the header, and adju= st > the exports so this new symbol is exported at GLIBCXX_3.4.32 not > GLIBCXX_3.4.31 N.B. this is what we do for glibc-based linux targets. The symbol is presen= t in the library even when glibc doesn't provide strtof128. This means that we d= on't have a different set of exported symbols when built on old or new glibc. If Solaris is ever going to get support for strtof128 and other _Float128 support then that is probably what we should do here as well.=