public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-2699] libstdc++: Do not use nullptr in C++03-compatible code
@ 2022-09-16 15:02 Jonathan Wakely
  0 siblings, 0 replies; only message in thread
From: Jonathan Wakely @ 2022-09-16 15:02 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

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()

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-09-16 15:02 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-16 15:02 [gcc r13-2699] libstdc++: Do not use nullptr in C++03-compatible code Jonathan Wakely

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).