From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 83AFD3858C36; Wed, 6 Mar 2024 13:48:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83AFD3858C36 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709732893; bh=a4SxnsKWyTiVzadwdp2gElbTz8MwqgYjLgwzdYH7SQk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wXFDVX6R6JITqRL6v1GgOAcGYOwH6dSdFFqdykk8MkTpp2Nq+pXTKDJVNwJUmdNzn hjGRB2EMPLztfws9k8TTnHKJRqEnIWH6XAj8orj5MORi6ubXDvRidK8AOn3rzqGexk +WWZ3nPpkzmORBNkfBYcLCdgVqRTOBMbmc0dgfAc= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111632] gcc fails to bootstrap when using libc++ Date: Wed, 06 Mar 2024 13:48:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: redi 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: 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=3D111632 --- Comment #12 from Jonathan Wakely --- (In reply to Dimitry Andric from comment #10) > Note there are other issues with poisoned identifiers, so I'll ask again:= is > a non-bootstrapped build even supposed to work, and officially supported,= or > not? Yes. > Or more qualified, is a non-bootstrapped build only officially supported > when building on a host with gcc and libstdc++? No. But just because something is officially supported doesn't mean it's a high priority for everybody involved. Some things just take longer to resolve.=