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 18:37:40 +0000	[thread overview]
Message-ID: <bug-107795-4-gn7BFxWJh1@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 #4 from Louis Dionne <ldionne.2 at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> You should not be building on top of GCC's limits.h header at all really.
> Rather implementations should have their own.

What do you mean by "implementations"? Do you mean implementations of the C
library or compiler implementations, or what?


(In reply to Jonathan Wakely from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Rather implementations should have their own.
> 
> Or just use GCC's one without change, which is what libstdc++ does. We don't
> provide any <limits.h> in libstdc++, only <climits>. When you #include
> <limits.h> with G++ you just get GCC's own <limits.h> as-is.

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`?

  parent reply	other threads:[~2022-11-21 18:37 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 [this message]
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
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-gn7BFxWJh1@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).