public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldionne.2 at gmail dot com" <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 21:52:51 +0000 [thread overview]
Message-ID: <bug-107795-4-7EuIrGC1sS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107795-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795
--- Comment #11 from Louis Dionne <ldionne.2 at gmail dot com> ---
(In reply to Andrew Pinski from comment #9)
>
> GCC version specific includes > GCC version specific fixincludes > C library
> includes
>
> That is for C.
> C++ is:
> libstdc++ library includes > ... (rest same as C).
Okay, that's great. That's exactly what I want! I want to be able to do:
libc++ library includes > ... (rest same as C)
What I'm trying to say is precisely that this doesn't work as intended today,
because somewhere inside "rest same as C", a header is taking for granted that
libstdc++ does NOT implement a <limits.h> header. If it did, then libstdc++
would get the same issue that we are having.
Is there a reason why GCC needs to indirect through <syslimits.h> and
recursively include <limits.h>, telling it to recurse using _GCC_NEXT_LIMITS_H?
next prev parent reply other threads:[~2022-11-21 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 15:59 [Bug libstdc++/107795] New: " ldionne.2 at gmail dot com
2022-11-21 16:07 ` [Bug bootstrap/107795] " pinskia at gcc dot gnu.org
2022-11-21 16:11 ` pinskia at gcc dot gnu.org
2022-11-21 16:57 ` redi at gcc dot gnu.org
2022-11-21 18:37 ` ldionne.2 at gmail dot com
2022-11-21 18:48 ` pinskia at gcc dot gnu.org
2022-11-21 18:49 ` redi at gcc dot gnu.org
2022-11-21 18:50 ` pinskia at gcc dot gnu.org
2022-11-21 18:58 ` ldionne.2 at gmail dot com
2022-11-21 19:02 ` pinskia at gcc dot gnu.org
2022-11-21 19:05 ` pinskia at gcc dot gnu.org
2022-11-21 21:52 ` ldionne.2 at gmail dot com [this message]
2022-11-21 22:02 ` pinskia at gcc dot gnu.org
2022-11-21 23:21 ` ldionne.2 at gmail dot com
2022-11-22 0:05 ` pinskia at gcc dot gnu.org
2022-11-22 0:37 ` redi at gcc dot gnu.org
2022-11-22 0:51 ` redi at gcc dot gnu.org
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-107795-4-7EuIrGC1sS@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).