From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 018193858C5F; Thu, 29 Feb 2024 15:10:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 018193858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709219442; bh=w5pzxCRRVAHtRqlaJ76DVS8l3IPAqrNyCX9lZfm88N4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=tNJ3jMMStHKRo7YV+uuO8lpMVnVZdTlZzq6yP5+JO7RB9Y6CKz7/oNwsUZbLrRoD3 udjMQp7JeuPNwLxSjW/TdW3lZ39Oq04u7JofHZItNIfg7VSMlSNv7xzhq/d1gWIlwe 4A466a1ADzXU3e6enR+QMRHZws6H+/9To6pg5HKM= From: "dimitry at andric dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111632] gcc fails to bootstrap when using libc++ Date: Thu, 29 Feb 2024 15:10:41 +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: dimitry at andric 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: 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 #10 from Dimitry Andric --- Note there are other issues with poisoned identifiers, so I'll ask again: i= s a non-bootstrapped build even supposed to work, and officially supported, or = not? Or more qualified, is a non-bootstrapped build only officially supported wh= en building on a host with gcc and libstdc++? Otherwise, keeping this bug open makes no real sense, as there seems to be = no movement at all on committing this patch. And it would make no sense to post any follow-up patches either.=