public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114869] GCC says nullptr_t is a C built in but it should be in <stddef.h> Date: Mon, 29 Apr 2024 21:22:33 +0000 [thread overview] Message-ID: <bug-114869-4-lVfzqLW7iU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114869-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114869 Joseph S. Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-04-29 CC| |mpolacek at gcc dot gnu.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- I suspect /* C-specific nullptr initialization. */ record_builtin_type (RID_MAX, "nullptr_t", nullptr_type_node); in c-decl.cc, from the original nullptr support for C.
next prev parent reply other threads:[~2024-04-29 21:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-26 20:14 [Bug c/114869] New: " eggert at cs dot ucla.edu 2024-04-29 21:22 ` jsm28 at gcc dot gnu.org [this message] 2024-04-29 21:25 ` [Bug c/114869] " mpolacek 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-114869-4-lVfzqLW7iU@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: linkBe 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).