public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Delete gdb::unique_ptr/gdb::move
Date: Tue, 15 Nov 2016 22:01:00 -0000	[thread overview]
Message-ID: <5cc8c7310338224d65aa14c4256d4d7539e0dd45@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 5cc8c7310338224d65aa14c4256d4d7539e0dd45 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5cc8c7310338224d65aa14c4256d4d7539e0dd45

Delete gdb::unique_ptr/gdb::move

Now that we require C++11 and all uses of gdb::unique_ptr and
gdb::move are gone, let's remove their definitions...

With my lazy hat on, I repurposed the header for "generally useful
unique_ptr specializations", and left gdb::unique_xmalloc_ptr in
there.  Not sure whether we it'd be better move it out of the gdb
namespace or leave it be.  I left it because it's less work and avoids
disrupting yet-unmerged patches that use it.

gdb/ChangeLog:
2016-11-15  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h: Update comment.
	* common/gdb_unique_ptr.h: Update header comment and copyright
	year.
	(gdb::unique_ptr, gdb::move): Delete.


             reply	other threads:[~2016-11-15 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 22:01 sergiodj+buildbot [this message]
2016-11-15 22:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2016-11-15 23:26 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-11-16  4:03 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-11-22 16:09 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-11-22 18:16 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-26 15:57 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-26 17:08 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-11-26 19:08 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot

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=5cc8c7310338224d65aa14c4256d4d7539e0dd45@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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).