public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95700] read-md.c: "missing sentinel in function call" when building gcc with musl
Date: Tue, 16 Jun 2020 16:40:02 +0000	[thread overview]
Message-ID: <bug-95700-4-N9NbkLykMY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95700-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
To be really safe during stage 1, GCC should not use NULL as a pointer sentinel
in C++ code anyway.

The bootstrap compiler could define it to 0 or 0u, neither of which is
guaranteed to be OK to pass as a varargs sentinel where a null pointer is
expected. Any of (void*)0 or (void*)NULL or nullptr would be safe.

  parent reply	other threads:[~2020-06-16 16:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 15:47 [Bug c++/95700] New: " iii at linux dot ibm.com
2020-06-16 15:55 ` [Bug c++/95700] " jakub at gcc dot gnu.org
2020-06-16 16:14 ` redi at gcc dot gnu.org
2020-06-16 16:22 ` redi at gcc dot gnu.org
2020-06-16 16:29 ` iii at linux dot ibm.com
2020-06-16 16:35 ` iii at linux dot ibm.com
2020-06-16 16:40 ` redi at gcc dot gnu.org [this message]
2020-06-17 13:31 ` iii at linux dot ibm.com
2020-06-17 18:51 ` iii at linux dot ibm.com
2020-07-02 10:39 ` cvs-commit at gcc dot gnu.org
2020-07-09 23:33 ` vvinayag at arm dot com
2020-07-10  9:14 ` iii at linux dot ibm.com
2020-07-11 11:12 ` iii at linux dot ibm.com
2020-07-17 22:21 ` vvinayag at arm dot com
2020-07-20  9:58 ` iii at linux dot ibm.com
2020-07-20 18:38 ` vvinayag at arm dot com
2020-07-21 22:05 ` iii at linux dot ibm.com
2020-07-22 21:47 ` iii at linux dot ibm.com
2020-07-22 23:06 ` vvinayag at arm dot com
2020-07-23 15:29 ` vvinayag at arm dot com
2020-07-23 15:39 ` vvinayag at arm dot com
2021-12-17  5:49 ` pinskia at gcc dot gnu.org
2024-04-14  4:09 ` [Bug bootstrap/95700] " pinskia 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-95700-4-N9NbkLykMY@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).