From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B89B53858D35; Thu, 29 Jun 2023 16:28:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B89B53858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1688056130; bh=Ep6TUJbnQ8pfCS5nR3AuLKUvQsHO8jtAXFITamV4yac=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gOZo7QQSL0PXWR372ih1//3RKh3bRj9QX+L+up1lva0VqN++B2yqkHDo5LPj7kCKK S8EAV0uLN0Txiwe1D/xR9iH6LSUMkA+OYXsE/fO1aOt7RyvgeHE0NZI+wiMDEGG7/S vvVphoe74M6Hq1BMNW2IXxDjDqacTHqwAhQ3UGiw= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110432] macOS: Segmentation fault when using stdlibc++ from gcc 13.1 in combination with clang-16 Date: Thu, 29 Jun 2023 16:28:50 +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: 13.1.0 X-Bugzilla-Keywords: ABI X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.2 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=3D110432 --- Comment #11 from Jonathan Wakely --- (In reply to Iain Sandoe from comment #10) > do all the other (I guess non-embedded) platforms now have init priority > support? It's OK if they don't, as long as (1) the attribute tells the truth, and (2) clang doesn't support it where gcc doesn't. It's fine to have no init_priority support, the library handles that OK.=