public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 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 13:35:30 +0000 [thread overview]
Message-ID: <bug-112699-4-pRl8OCCYBI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112699-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112699
--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #1)
> Can you clarify which file you mean? gcc/ginclude does not have a limits.h.
>
> I assume you are not talking about the fixinclude'd limits.h?
No, I mean the limits.h in $(dirname $(gcc -print-libgcc-file-name)). It
currently contains these lines to include libc limits.h:
#ifndef _LIBC_LIMITS_H_
/* Use "..." so that we find syslimits.h only in this same directory. */
#include "syslimits.h"
#endif
(if libc limits.h is fixinclude'd, it will be saved to syslimits.h; otherwise
syslimits.h will just contain "#include_next <limits.h>".)
And I'm asking if
#ifndef _LIBC_LIMITS_H_ && !__STDC_HOSTED__
/* Use "..." so that we find syslimits.h only in this same directory. */
#include "syslimits.h"
#endif
would be better?
prev parent reply other threads:[~2023-11-24 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:36 [Bug c/112699] New: " xry111 at gcc dot gnu.org
2023-11-24 11:15 ` [Bug c/112699] " amonakov at gcc dot gnu.org
2023-11-24 11:24 ` amonakov at gcc dot gnu.org
2023-11-24 13:35 ` xry111 at gcc dot gnu.org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112699-4-pRl8OCCYBI@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).