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 AB7233860744; Mon, 21 Nov 2022 19:02:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AB7233860744
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669057320;
	bh=eqjMk7cIQ8PYNaaOrDLwh/T2FC58E0E/0gI2KlOaPXI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mOe9UekiFuINCvHf6bxeyk2C7cYz2lDhZ/KVGGrgqnOVjy1v4HWoRO9nPCMYYh2rH
	 JgNUTLDg35jgm1JQvYMZY3uj835XCzBX5vcSuWZVzQwb65GXt3J02r/6g9hsUJfj7e
	 thaVJQ7sF6YKY7OedJUjL4OTKA0M22+oJfcLxSyQ=
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 19:02:00 +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-BoqDpBMtA2@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 #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Louis Dionne from comment #8)
> (In reply to Andrew Pinski from comment #5)
> > (In reply to Louis Dionne from comment #4)
> > > (In reply to Andrew Pinski from comment #2)
> > > > You should not be building on top of GCC's limits.h header at all r=
eally.
> > > > Rather implementations should have their own.
> > >=20
> > > What do you mean by "implementations"? Do you mean implementations of=
 the C
> > > library or compiler implementations, or what?
> >=20
> > GCC limits.h is the implementation detail of GCC.
> > Yes I know it gets fuzzy. This is why GCC even has fixincludes to make =
sure
> > target headers are always correct. See the comment I posted.
>=20
> When compiling pure C with GCC, what's the order of includes? Is it "C
> Library includes > GCC builtin includes", or "GCC builtin includes > C
> Library includes"?

GCC version specific includes > GCC version specific fixincludes > C library
includes

That is for C.
C++ is:
libstdc++ library includes > ... (rest same as C).=