From: Simon Marchi <simon.marchi@polymtl.ca>
To: "周春明(日月)" <riyue.zcm@alibaba-inc.com>,
Gdb-patches
<gdb-patches-bounces+riyue.zcm=alibaba-inc.com@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>
Cc: Louis-He <1726110778@qq.com>,
Dominique Quatravaux <dominique.quatravaux@epfl.ch>,
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: Tue, 1 Mar 2022 09:32:09 -0500 [thread overview]
Message-ID: <46908d9f-d3bf-bd2f-3a63-1d8429ac8ab8@polymtl.ca> (raw)
In-Reply-To: <65ee9ce9-34db-4434-9cc6-34378f96bee9.riyue.zcm@alibaba-inc.com>
On 2022-03-01 02:48, 周春明(日月) wrote:
>
> Hi GDB maintainers,
>
> I tried to build new GDB12, but encounter below error, anyone could tell me how to fix it? Thanks!
>
> CXX new-op.o
>
> *../../gdbsupport/new-op.cc:32:13:* *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]
>
> extern void operator delete (void *p, std::size_t) noexcept;
>
> * ^*
>
> *../../gdbsupport/new-op.cc:33:13:* *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]
>
> extern void operator delete[] (void *p, std::size_t) noexcept;
>
> * ^*
>
> *../../gdbsupport/new-op.cc:119: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]
>
> operator delete (void *p, std::size_t) noexcept
>
> * ^*
>
> *../../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]
>
> operator delete[] (void *p, std::size_t) noexcept
Hi,
Can you give a bit more info?
- compiler and compiler version
- OS and OS version
- your complete configure line
- the build command line for that file, given by "make V=1"
Simon
next prev parent reply other threads:[~2022-03-01 14:32 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 [this message]
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
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=46908d9f-d3bf-bd2f-3a63-1d8429ac8ab8@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=1726110778@qq.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 \
/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).