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 755393858D35; Thu, 29 Jun 2023 16:09:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 755393858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688054942;
	bh=fx2c/8ix3GBoIduqLI7HQb8giM8RP1y67M7inppZWWM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fQJNIfSZloByMrJwbUNKgXdioh8DMV9xBEfj1F3pjkIeW4FIzRisOv//Sxo4GDoOG
	 iVLNX8ryF+0knkn/oaY+a3bkZR0HXcOkPCvqCSC9cjSunj8XlJOYR5gQCf/30JTads
	 CgnVbAbpUopnpZ335D3RrKK4AP5kvziOrmDU4tys=
From: "ppalka at gcc dot gnu.org" <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: Thu, 29 Jun 2023 16:09:02 +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: ppalka 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: bug_status target_milestone assigned_to
Message-ID: <bug-110432-4-EA2IAii3Y2@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

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Target Milestone|---                         |13.2
           Assignee|unassigned at gcc dot gnu.org      |ppalka at gcc dot g=
nu.org

--- Comment #9 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> 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.

Yes, sorry for letting this issue slip through the cracks.  It makes sense =
to
fix this by simply disabling the <iostream> optimization on macOS as you
suggested, and perhaps worry about a configure-time check only if it turns =
out
another platform hits this issue.=