From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: "Andrew Burgess" <aburgess@redhat.com>,
"周春明(日月)" <riyue.zcm@alibaba-inc.com>,
"Simon Marchi" <simon.marchi@polymtl.ca>,
Gdb-patches
<gdb-patches-bounces+riyue.zcm=alibaba-inc.com@sourceware.org>,
"Dominique Quatravaux" <dominique.quatravaux@epfl.ch>,
Louis-He <1726110778@qq.com>,
"Sam Warner" <samuel.r.warner@me.com>
Subject: Re: ../../gdbsupport/new-op.cc:137:1: error: ‘void operator delete [](void*, std::size_t)’ is a usual (non-placement) deallocation function in C++14 (or with -fsized-deallocation) [-Werror=c++14-compat]
Date: Thu, 03 Mar 2022 07:18:15 -0700 [thread overview]
Message-ID: <8735jzw254.fsf@tromey.com> (raw)
In-Reply-To: <e9366ef9-a1e1-7bfb-77d6-7ead3ae1f375@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Wed, 2 Mar 2022 12:41:11 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>> Just for my sanity, GDB currently targets C++11, right? But, I guess
>> you're suggesting you'd like to keep these functions in place so we
>> _can_ compile with C++14 if we want?
Simon> That was my idea, yes. We require GDB to be buildable in C++11, but we
Simon> also regularly build it in C++14 and C++17 as well, since recent
Simon> compilers default to that version (and we don't force
Simon> -std=c++11/-std=gnu++11).
We even have code that takes advantage of this, like gdb_string_view.h:
#if __cplusplus >= 201703L
#include <string_view>
Tom
prev parent reply other threads:[~2022-03-03 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:48 周春明(日月)
2022-03-01 14:32 ` Simon Marchi
2022-03-02 3:08 ` 回复：../../gdbsupport/new-op.cc:137:1: " 周春明(日月)
2022-03-02 16:45 ` Simon Marchi
2022-03-02 16:30 ` ../../gdbsupport/new-op.cc:137:1: " Andrew Burgess
2022-03-02 16:54 ` Simon Marchi
2022-03-02 17:03 ` Pedro Alves
2022-03-02 17:26 ` Simon Marchi
2022-03-02 17:43 ` Pedro Alves
2022-03-02 17:22 ` Andrew Burgess
2022-03-02 17:41 ` Simon Marchi
2022-03-03 12:27 ` Andrew Burgess
2022-03-03 14:18 ` Tom Tromey [this message]
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=8735jzw254.fsf@tromey.com \
--to=tom@tromey.com \
--cc=1726110778@qq.com \
--cc=aburgess@redhat.com \
--cc=dominique.quatravaux@epfl.ch \
--cc=gdb-patches-bounces+riyue.zcm=alibaba-inc.com@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=riyue.zcm@alibaba-inc.com \
--cc=samuel.r.warner@me.com \
--cc=simon.marchi@polymtl.ca \
/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).