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: Wed, 2 Mar 2022 11:45:28 -0500 [thread overview]
Message-ID: <6d70655f-22eb-96fd-85e8-ebe609dfe533@polymtl.ca> (raw)
In-Reply-To: <460c98ca-9e94-401b-8838-d6273ac2b641.riyue.zcm@alibaba-inc.com>
> Hi,
>
> Can you give a bit more info?
> [David] of course.
>
> - compiler and compiler version
> [David]
>
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
>
>
> - OS and OS version
> [David]
>
> 16.04.1-Ubuntu
>
>
> - your complete configure line
> [David]
>
> ../configure --enable-64-bit-bfd --enable-targets="x86_64-linux-gnu,alippu-unknown-unknown" --disable-ld --disable-gas --disable-gdbserver --disable-sim --enable-tui --disable-gdbtk --disable-shared --with-expat --with-system-zlib --without-guile --with-lzma --with-python=python3
>
>
> - the build command line for that file, given by "make V=1"
> [David]
>
> g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I../../gdbsupport -I../../gdbsupport/../include -I../../gdbsupport/../gdb -I../gnulib/import -I../../gdbsupport/../gnulib/import -I.. -I../../gdbsupport/.. -I../bfd -I../../gdbsupport/../bfd -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-variable -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-error=maybe-uninitialized -Wsuggest-override -Wmissing-declarations -Wstrict-null-sentinel -Wformat -Wformat-nonliteral -Werror -g -O2 -MT new-op.o -MD -MP -MF .deps/new-op.Tpo -c -o new-op.o ../../gdbsupport/new-op.cc
Thanks, it seems like Andrew managed to reproduce the problem with this
information, I'll reply to his message.
Simon
next prev parent reply other threads:[~2022-03-02 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:48 ../../gdbsupport/new-op.cc:137:1: " 周春明(日月)
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 [this message]
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=6d70655f-22eb-96fd-85e8-ebe609dfe533@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).