From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH v2 0/3] Poison obstack functions
Date: Sat, 28 Apr 2018 03:31:00 -0000 [thread overview]
Message-ID: <20180428033121.20163-1-simon.marchi@polymtl.ca> (raw)
v2 of https://sourceware.org/ml/gdb-patches/2018-04/msg00524.html
What's new:
- Don't allocate mapped_index on an obstack (patch 1/3)
- Use OBSTACK_ZALLOC instead of XOBNEW + memset when possible (patch
3/3)
Simon Marchi (3):
Don't allocate mapped_index on the objfile obstack
Introduce obstack_new, poison other "typed" obstack functions
Use XOBNEW/XOBNEWVEC/OBSTACK_ZALLOC when possible
gdb/ada-lang.c | 3 +--
gdb/common/poison.h | 31 +++++++++++++++++++++++-
gdb/common/traits.h | 8 ++++++
gdb/dwarf2-frame.c | 3 +--
gdb/dwarf2read.c | 14 +++--------
gdb/dwarf2read.h | 2 +-
gdb/gdb_obstack.h | 36 ++++++++++++++++++++++++---
gdb/gdbarch.c | 9 ++-----
gdb/gdbarch.h | 10 +++++---
gdb/gdbarch.sh | 21 ++++++++--------
gdb/hppa-tdep.c | 7 ++----
gdb/mdebugread.c | 51 +++++++++++++--------------------------
gdb/minsyms.c | 6 ++---
gdb/objfiles.c | 9 ++-----
gdb/psymtab.c | 4 +--
gdb/stabsread.c | 7 ++----
gdb/target-descriptions.c | 7 +-----
gdb/xcoffread.c | 3 +--
18 files changed, 125 insertions(+), 106 deletions(-)
--
2.17.0
next reply other threads:[~2018-04-28 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 3:31 Simon Marchi [this message]
2018-04-28 3:31 ` [PATCH v2 2/3] Introduce obstack_new, poison other "typed" " Simon Marchi
2018-04-28 3:31 ` [PATCH v2 1/3] Don't allocate mapped_index on the objfile obstack Simon Marchi
2018-04-28 3:31 ` [PATCH v2 3/3] Use XOBNEW/XOBNEWVEC/OBSTACK_ZALLOC when possible Simon Marchi
2018-05-21 3:00 ` [PATCH v2 0/3] Poison obstack functions Simon Marchi
2018-05-21 3:23 ` Simon Marchi
2018-05-21 8:53 ` [pushed] Fix copy-pasto, allocate objfile_per_bfd_storage with obstack_new Simon Marchi
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=20180428033121.20163-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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