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 9857E3861029; Mon, 21 Nov 2022 18:50:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9857E3861029
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669056655;
	bh=LE/fGiOnIUaZrtErM3AH6QM+1OpUMhDTnLyYl93JrTo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Nc6Rwt9c3Ay9SDJyf1FbwU+2WkHJerCbHlUkQA39Iy9CDsU0HZSVLPaI+jOOppUWq
	 fjmbt+0sCRRnUu6nN5zZLhU1ts22d4KmmXkWJyIC3yzRpAz/tQHBELuPruhfOpxcaO
	 jAHvcQB5Ay4bIvJeqdYG/vrLf7Pw0Smn+c9015Sk=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107795] <limits.h> recursion through <syslimits.h>
 breaks non-GNU implementations of the C++ stdlib
Date: Mon, 21 Nov 2022 18:50:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 12.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-107795-4-dCCQ0YDKV0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107795-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=3D107795

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Louis Dionne from comment #4)
> Yeah but we may need to add stuff to <limits.h> on some platforms, so we =
may
> need to have such a header. Also, I assume you only do that for a subset =
of
> headers, because you must have <foo.h> headers in libstdc++ for a few
> headers that require adding const-correct overloads of e.g. `memchr`?

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D30928 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D33935 for those issues there=
.=