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 2E8053858C78; Thu,  8 Feb 2024 11:00:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E8053858C78
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707390033;
	bh=fYkvrEiLNMYS2NYEUdiAij/xxAa6RnwK9ZtDJcbth9E=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fuAfsuil3jdyc4dcX1gPbYvW6m4ogr/UjLldvetqi59Pd4gWhkHfBERb6mw0fLlK7
	 o+k0rC/LTeuA5EXSfJySpHcSX39rhxcAmOxNKIVjP9/lWWZfixZIbpj6PyYonIdHCL
	 ZRJNZw3FwCMQOBlUzAEUUuhJyGnBG7MAGpO8S93w=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.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 11:00:32 +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: jakub 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: <bug-111632-4-D2FZ3SJzDf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111632-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111632-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=3D111632

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Arsen Arsenovi=C4=87 from comment #7)
> hm, somewhat unrelated to the patch, but is there any reason why stage 1
> needs 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)

I certainly work on stage 1 all the time, that is where I develop everythin=
g I
do
(of course once something is written, I test it with full bootstrap, but
discovering issues there is too late).
Non-bootstrapped compiler has the added bonus that it defaults to -O0 -g
building of objects when they are rebuilt when doing make inside of the gcc
directory.=