From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH] Avoid an allocation in attr_to_dynamic_prop
Date: Sun, 4 Feb 2024 12:15:59 -0700 [thread overview]
Message-ID: <20240204191559.4007457-1-tom@tromey.com> (raw)
I noticed that attr_to_dynamic_prop allocates a dwarf_block, when no
allocation is required. This patch stack-allocates the object
instead.
---
gdb/dwarf2/read.c | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index e873d9cc440..34bbb6e804d 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -15385,24 +15385,23 @@ attr_to_dynamic_prop (const struct attribute *attr, struct die_info *die,
baton->locexpr.per_cu = cu->per_cu;
baton->locexpr.per_objfile = per_objfile;
- struct dwarf_block *block;
+ struct dwarf_block block;
if (attr->form == DW_FORM_data16)
{
size_t data_size = 16;
- block = XOBNEW (obstack, struct dwarf_block);
- block->size = (data_size
- + 2 /* Extra bytes for DW_OP and arg. */);
- gdb_byte *data = XOBNEWVEC (obstack, gdb_byte, block->size);
+ block.size = (data_size
+ + 2 /* Extra bytes for DW_OP and arg. */);
+ gdb_byte *data = XOBNEWVEC (obstack, gdb_byte, block.size);
data[0] = DW_OP_implicit_value;
data[1] = data_size;
memcpy (&data[2], attr->as_block ()->data, data_size);
- block->data = data;
+ block.data = data;
}
else
- block = attr->as_block ();
+ block = *attr->as_block ();
- baton->locexpr.size = block->size;
- baton->locexpr.data = block->data;
+ baton->locexpr.size = block.size;
+ baton->locexpr.data = block.data;
switch (attr->name)
{
case DW_AT_string_length:
--
2.43.0
next reply other threads:[~2024-02-04 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 19:15 Tom Tromey [this message]
2024-02-05 4:36 ` Tom de Vries
2024-02-05 19:12 ` 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=20240204191559.4007457-1-tom@tromey.com \
--to=tom@tromey.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).