public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>, Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] New gdb::make_unique and more std::unique_ptr use
Date: Mon, 14 Aug 2023 14:42:31 +0100	[thread overview]
Message-ID: <cover.1692019711.git.aburgess@redhat.com> (raw)

This started while working on another series, in order to avoid
calling 'new' directly, I really wanted a std::make_unique function --
but that's C++14, so not available for GDB right now.

So I added a gdb::make_unique, which should be equivalent to the C++14
function.

The last two commits are additional make_unique/unique_ptr changes,
but target specific areas that needed slightly more refactoring.

---

Andrew Burgess (3):
  gdb: add gdb::make_unique function
  gdb: have mi_out_new return std::unique_ptr
  gdb: remove mi_parse::make functions

 gdb/addrmap.c                          |  2 +-
 gdb/break-catch-load.c                 |  5 +-
 gdb/compile/compile-c-support.c        |  2 +-
 gdb/cp-name-parser.y                   |  2 +-
 gdb/cp-support.c                       |  2 +-
 gdb/dwarf2/frame.c                     |  2 +-
 gdb/dwarf2/read-debug-names.c          |  2 +-
 gdb/dwarf2/read-gdb-index.c            |  2 +-
 gdb/dwarf2/read.c                      |  2 +-
 gdb/gdbtypes.c                         |  2 +-
 gdb/mi/mi-interp.c                     |  2 +-
 gdb/mi/mi-main.c                       |  4 +-
 gdb/mi/mi-out.c                        |  8 +--
 gdb/mi/mi-out.h                        |  2 +-
 gdb/mi/mi-parse.c                      | 76 ++++++++++++--------------
 gdb/mi/mi-parse.h                      | 18 ++----
 gdb/python/py-mi.c                     |  4 +-
 gdb/python/py-varobj.c                 |  4 +-
 gdb/ui-out.c                           |  8 +--
 gdb/unittests/parallel-for-selftests.c |  4 +-
 gdb/varobj.c                           |  2 +-
 gdbsupport/gdb_unique_ptr.h            |  9 +++
 22 files changed, 78 insertions(+), 86 deletions(-)


base-commit: 86dfe011797b3e442622d427e9abd1e0f70f3a62
-- 
2.25.4


             reply	other threads:[~2023-08-14 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 13:42 Andrew Burgess [this message]
2023-08-14 13:42 ` [PATCH 1/3] gdb: add gdb::make_unique function Andrew Burgess
2023-08-14 15:38   ` Tom Tromey
2023-08-17 10:26     ` Andrew Burgess
2023-08-17 18:07       ` Tom Tromey
2023-08-21 10:02         ` Andrew Burgess
2023-08-14 13:42 ` [PATCH 2/3] gdb: have mi_out_new return std::unique_ptr Andrew Burgess
2023-08-14 13:42 ` [PATCH 3/3] gdb: remove mi_parse::make functions Andrew Burgess
2023-08-22 15:33 ` [PATCH 0/3] New gdb::make_unique and more std::unique_ptr use Tom Tromey
2023-08-23  8:52   ` Andrew Burgess

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=cover.1692019711.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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).