public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 16:11:20 +0000	[thread overview]
Message-ID: <bug-107795-4-4tpzu2kY64@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 #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>This recursive inclusion with a macro is hostile to implementations that want to build on top of GCC's <limits.h> header

You should not be building on top of GCC's limits.h header at all really.
Rather implementations should have their own.

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