public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Make allocate_on_obstack a bit safer
Date: Tue, 27 Feb 2024 14:42:16 -0700	[thread overview]
Message-ID: <20240227-obstac-alloc-v1-0-bd079aad35cd@adacore.com> (raw)

This series makes the allocate_on_obstack mixin a little safer by
having it enforce the rule that an object allocated on an obstack must
have a trivial destructor.

---
Tom Tromey (3):
      Use addrmap_fixed in a few spots
      Don't use virtual destructor in addrmap
      Require trivial destructor in allocate_on_obstack

 gdb/addrmap.h             |  7 ++++---
 gdb/block.c               |  2 +-
 gdb/block.h               | 12 ++++++------
 gdb/dwarf2/cooked-index.h |  4 ++--
 gdb/dwarf2/read.h         |  2 +-
 gdb/gdbtypes.h            |  4 ++--
 gdb/symtab.h              |  2 +-
 gdbsupport/gdb_obstack.h  |  6 +++++-
 8 files changed, 22 insertions(+), 17 deletions(-)
---
base-commit: 407ca654547b100903f7eab44d078a2440736f13
change-id: 20240227-obstac-alloc-deabe0f935c3

Best regards,
-- 
Tom Tromey <tromey@adacore.com>


             reply	other threads:[~2024-02-27 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 21:42 Tom Tromey [this message]
2024-02-27 21:42 ` [PATCH 1/3] Use addrmap_fixed in a few spots Tom Tromey
2024-02-28 12:27   ` Alexandra Petlanova Hajkova
2024-02-27 21:42 ` [PATCH 2/3] Don't use virtual destructor in addrmap Tom Tromey
2024-02-28 15:16   ` Alexandra Petlanova Hajkova
2024-02-27 21:42 ` [PATCH 3/3] Require trivial destructor in allocate_on_obstack Tom Tromey
2024-02-28 16:55   ` Alexandra Petlanova Hajkova
2024-03-21 18:20 ` [PATCH 0/3] Make allocate_on_obstack a bit safer 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=20240227-obstac-alloc-v1-0-bd079aad35cd@adacore.com \
    --to=tromey@adacore.com \
    --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).