From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 40CE4385840F; Thu, 8 Feb 2024 10:56:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 40CE4385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707389809; bh=z8XTOFAUDZcXdLjbo2ChSje367/odibsMsb8z120JpU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Zy71ehvfBjKMrRzl7p6sMGi2Bm7ugc2ZjFg0nhx3RxfqQ3/KVUav6WlgUGQdOC0qC 0nbyopryNoGBvk+IVZXbi2oMxT97YtHKmZAVGDDda4snVEwkDcIDiz1zdsWmf95LkP IBTW2UskK57FvPHdaJCsS5epSmnBih4BvhHTXe9I= From: "arsen at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111632] gcc fails to bootstrap when using libc++ Date: Thu, 08 Feb 2024 10:56:47 +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: arsen 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: cc 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 Arsen Arsenovi=C4=87 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arsen at gcc dot gnu.org --- Comment #7 from Arsen Arsenovi=C4=87 --- hm, somewhat unrelated to the patch, but is there any reason why stage 1 ne= eds to have poisoning? AFAIK future stages won't use libcxx anyway, and nobody 'works' on stage 1, so I see no reason to poison the symbols there (unless bootstrap is disabled, I guess)=