Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH 3/8] Change fde table to a vector
Date: Wed, 12 Feb 2020 22:36:00 -0000	[thread overview]
Message-ID: <8736bfsaau.fsf@tromey.com> (raw)
In-Reply-To: <a8628675-5902-8923-d9c8-e294c6a317c1@simark.ca> (Simon Marchi's	message of "Tue, 11 Feb 2020 22:28:46 -0500")

>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:

Simon> As a further change, I think we could consider make this a vector
Simon> of objects, rather than a vector of pointers.

I think I'd rather leave this for a future change.
It makes the patch a lot less obvious, to me anyway.  find_fde returns a
pointer -- but is that safe?  I think so, but I am not 100% certain; but
with the current code it definitely is.

>> +const struct objfile_key<dwarf2_fde_table> dwarf2_frame_objfile_data;

Simon> Can you make this static, while at it?

I did this.

>> +  if (!fde_table.empty ())

Simon> If you want to simplify the code even further, you could get rid
Simon> of this check, since the code below should cope well with an
Simon> empty vector.

Thanks, I did this too.

>> +      fde_table2->shrink_to_fit ();

Simon> That shrink_to_fit appears to be pointless, as fde_table2 is
Simon> created empty and we only push_back.  Maybe you meant to create
Simon> it with an initial size?

IIUC push_back normally uses some resize factor; the shrink_to_fit is a
request to discard any excess memory allocated this way.

FWIW another thing that could be done in this code is to use the
remove_if to remove elements in-place from fde_table.  This is another
thing I'd rather do separately.

Tom


  parent reply	other threads:[~2020-02-12 22:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08 15:28 [PATCH 0/8] Share DWARF frame information across inferiors Tom Tromey
2020-02-08 15:28 ` [PATCH 8/8] Move the frame data to the BFD when possible Tom Tromey
2020-02-11 10:45   ` Luis Machado
2020-02-12  0:31     ` Tom Tromey
2020-11-14  3:31   ` Simon Marchi
2020-02-08 15:28 ` [PATCH 3/8] Change fde table to a vector Tom Tromey
     [not found]   ` <5a373a74-9283-5d82-a22d-7a2606a4d3f5@linaro.org>
2020-02-12  0:29     ` Tom Tromey
2020-02-12  3:28   ` Simon Marchi
2020-02-12  3:33     ` Simon Marchi
2020-02-12 22:36     ` Tom Tromey [this message]
2020-02-12 22:47       ` Simon Marchi
2020-02-08 15:28 ` [PATCH 4/8] Store the comp_unit instead of the FDE table Tom Tromey
2020-02-09 23:56   ` Christian Biesinger via gdb-patches
2020-02-12  0:19     ` Tom Tromey
2020-02-11 10:32   ` Luis Machado
2020-02-12  0:20     ` Tom Tromey
2020-02-12  3:36   ` Simon Marchi
2020-02-12 22:20     ` Tom Tromey
2020-02-08 15:28 ` [PATCH 7/8] Remove the objfile backlink from comp_unit Tom Tromey
2020-02-09 23:56   ` Christian Biesinger via gdb-patches
2020-02-12  0:26     ` Tom Tromey
2020-02-11 10:40   ` Luis Machado
2020-02-08 15:28 ` [PATCH 6/8] Remove a use of the comp_unit backlink Tom Tromey
2020-02-08 15:28 ` [PATCH 2/8] Dont' allow copying of auto_obstack Tom Tromey
2020-02-09 23:56   ` Christian Biesinger via gdb-patches
2020-02-12  0:16     ` Tom Tromey
2020-02-12  0:53       ` Simon Marchi
2020-02-12  1:01         ` Tom Tromey
2020-02-08 15:28 ` [PATCH 5/8] Add per-unit obstack Tom Tromey
2020-02-11 10:34   ` Luis Machado
2020-02-12  3:53   ` Simon Marchi
2020-02-12 22:41     ` Tom Tromey
2020-02-12 22:48       ` Simon Marchi
2020-02-12 22:51         ` Tom Tromey
2020-02-08 15:28 ` [PATCH 1/8] Don't forward-declare struct objfile in frame.h Tom Tromey
2020-02-12  0:51   ` Simon Marchi
2020-02-12  1:59     ` Tom Tromey
2020-02-08 15:29 ` [PATCH 0/8] Share DWARF frame information across inferiors 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=8736bfsaau.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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