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 65D6D3858CD1; Fri, 24 Nov 2023 11:24:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65D6D3858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700825081;
	bh=msj5sz1WypOlmtN0GB5YJWuSLwnTIxKSzfZLlTGPEaI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lSsi8PIKkFz5LirP8KF1BhSDdwzaB1GRqJKM+Ce+PsUEDVM8HJmfvs54zA2HgeVoo
	 GIaafwWPIq3QNapFJYAb0ZfYHiuNHcyYj1QRf7x5kXNmHIvFBTy3BluS3UgpkLlpxi
	 SYkEHi48bX3zW+Ncbjhv2moW6Q7UKhJsOp1xBqig=
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112699] Should limits.h in freestanding environment be
 self-contained?
Date: Fri, 24 Nov 2023 11:24:41 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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-112699-4-Y5KIZQhQ2C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112699-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=3D112699

--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Sorry, even though GCC's limits.h is installed under include-fixed, it is
generated separately, not by the generic fixincludes mechanism. I was confu=
sed.=