public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-2699] libstdc++: Do not use nullptr in C++03-compatible code
Date: Fri, 16 Sep 2022 15:02:18 +0000 (GMT)	[thread overview]
Message-ID: <20220916150218.6546338155B2@sourceware.org> (raw)

https://gcc.gnu.org/g:5ad435f2a0d29486c917025dfa239b9b88c35a09

commit r13-2699-g5ad435f2a0d29486c917025dfa239b9b88c35a09
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Sep 16 14:27:43 2022 +0100

    libstdc++: Do not use nullptr in C++03-compatible code
    
    This has to be valid as C++98/C++03.
    
    libstdc++-v3/ChangeLog:
    
            * include/debug/formatter.h [_GLIBCXX_DEBUG_BACKTRACE]
            (_Error_formatter): Use 0 as null pointer constant.

Diff:
---
 libstdc++-v3/include/debug/formatter.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/libstdc++-v3/include/debug/formatter.h b/libstdc++-v3/include/debug/formatter.h
index b4b72383e22..f120163c6d4 100644
--- a/libstdc++-v3/include/debug/formatter.h
+++ b/libstdc++-v3/include/debug/formatter.h
@@ -609,8 +609,7 @@ namespace __gnu_debug
     , _M_function(__function)
 #if _GLIBCXX_HAVE_STACKTRACE
 # ifdef _GLIBCXX_DEBUG_BACKTRACE
-    , _M_backtrace_state(
-      __glibcxx_backtrace_create_state(nullptr, 0, nullptr, nullptr))
+    , _M_backtrace_state(__glibcxx_backtrace_create_state(0, 0, 0, 0))
     , _M_backtrace_full(&__glibcxx_backtrace_full)
 # else
     , _M_backtrace_state()

                 reply	other threads:[~2022-09-16 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220916150218.6546338155B2@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).