From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 3908E3858D37; Tue, 27 Jun 2023 10:32:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3908E3858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687861933;
	bh=Gfj6EbAHRJTf4mS6XRCQfHm7u9ldKZ/T6v+tr/wT6NE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vHs0gqqSKznrdOZAV7FL3zYq/zIeRr+wqvvS0fNgVaA/n8hExiMu1Enh65sMvzUw5
	 D0nLU/RfKMJnpIVL7VZdZS8Ktsv4TXiZpU9gShJ+xl8yoXcSVQz3ews+Prt41Q5Uq3
	 odaNzmPuN9ZTPLqWSWMBj7zPngJJAdlfLO4I8Nog=
From: "sascha.scandella at dentsplysirona dot com" <gcc-bugzilla@gcc.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: Tue, 27 Jun 2023 10:32:12 +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: sascha.scandella at dentsplysirona dot com
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: <bug-110432-4-VYgIue81dU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110432-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110432-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110432

--- Comment #2 from Sascha Scandella <sascha.scandella at dentsplysirona do=
t com> ---
> Still libstdc++ ;-)

True that ;-)

> Patrick, we talked about this and IIRC your suggestion was to move the
> __has_attribute check into configure, so that it depends on GCC, not on
> whichever compiler happens to include <iostream> later.

I think this would also be a solution. Would this then be included in a fut=
ure
GCC 13.2? Took quite a while until I figured out the reason for the segfaul=
t.

Just for completeness sake. I also posted it on one of the brew repositories
for GCC. Probably this could be patched on macOS also for GCC 13.1.
https://github.com/iains/gcc-13-branch/issues/6=