From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Fix various C++ related clang warnings
Date: Wed, 23 Nov 2016 20:07:00 -0000 [thread overview]
Message-ID: <20161123200652.89209-1-jhb@FreeBSD.org> (raw)
These patches fix various new C++ warnings reported by clang 3.8.0.
The last one regarding std::move is a bit surprising I think, but
there's a not-bad answer to a similar issue here:
http://stackoverflow.com/questions/19267408/why-does-stdmove-prevent-rvo
John Baldwin (3):
Fix mismatched struct vs class tags.
Add noexcept to custom non-throwing new operators.
Do not use std::move when assigning an anonymous object to a
unique_ptr.
gdb/ChangeLog | 27 +++++++++++++++++++++++++++
gdb/ada-lang.c | 6 +++---
gdb/ax-gdb.c | 8 ++++----
gdb/breakpoint.c | 8 ++++----
gdb/breakpoint.h | 2 +-
gdb/common/new-op.c | 4 ++--
gdb/dtrace-probe.c | 3 +--
gdb/mi/mi-main.c | 4 ++--
gdb/parse.c | 2 +-
gdb/tracepoint.c | 14 +++++++-------
gdb/tracepoint.h | 4 ++--
11 files changed, 54 insertions(+), 28 deletions(-)
--
2.9.2
next reply other threads:[~2016-11-23 20:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:07 John Baldwin [this message]
2016-11-23 20:08 ` [PATCH 2/3] Add noexcept to custom non-throwing new operators John Baldwin
2016-11-24 17:03 ` Pedro Alves
2016-11-23 20:08 ` [PATCH 3/3] Do not use std::move when assigning an anonymous object to a unique_ptr John Baldwin
2016-11-23 21:19 ` Simon Marchi
2016-11-23 23:31 ` John Baldwin
2016-11-24 0:08 ` Simon Marchi
2016-11-24 16:52 ` Pedro Alves
2016-11-23 20:08 ` [PATCH 1/3] Fix mismatched struct vs class tags John Baldwin
2016-11-23 20:58 ` Simon Marchi
2016-11-23 23:23 ` John Baldwin
2016-11-24 17:02 ` Pedro Alves
2016-11-24 17:47 ` John Baldwin
2016-11-24 18:50 ` Pedro Alves
2016-11-24 19:15 ` John Baldwin
2016-11-30 11:39 ` Pedro Alves
2016-11-30 16:23 ` John Baldwin
2016-11-30 16:38 ` Pedro Alves
2016-11-30 16:52 ` Simon Marchi
2016-11-30 16:51 ` Simon Marchi
2016-11-30 17:08 ` Pedro Alves
2016-11-30 17:54 ` Simon Marchi
2016-11-30 17:59 ` Eli Zaretskii
2016-11-23 22:18 ` [PATCH 0/3] Fix various C++ related clang warnings Simon Marchi
2016-11-23 23:23 ` John Baldwin
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=20161123200652.89209-1-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.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).