Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Have partial symbol tables own psymbol vectors
Date: Tue, 1 Sep 2020 10:41:02 -0400	[thread overview]
Message-ID: <74b64278-9789-9130-13fb-c722b06c09a9@simark.ca> (raw)
In-Reply-To: <87sgc27nez.fsf@tromey.com>

I went through the patch again, I think I understand it better and it looks good to me.

Even though there is slightly bigger memory usage, it's much easier to understand how
things are organized like this.

One question here:

> @@ -1666,16 +1605,6 @@ add_psymbol_to_list (gdb::string_view name, bool copy_name,
>  void
>  init_psymbol_list (struct objfile *objfile, int total_symbols)
>  {
> -  if (objfile->partial_symtabs->global_psymbols.capacity () == 0
> -      && objfile->partial_symtabs->static_psymbols.capacity () == 0)
> -    {
> -      /* Current best guess is that approximately a twentieth of the
> -	 total symbols (in a debugging file) are global or static
> -	 oriented symbols, then multiply that by slop factor of
> -	 two.  */
> -      objfile->partial_symtabs->global_psymbols.reserve (total_symbols / 10);
> -      objfile->partial_symtabs->static_psymbols.reserve (total_symbols / 10);
> -    }
>  }

Did you keep this empty function on purpose?

Simon


  parent reply	other threads:[~2020-09-01 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 19:33 Tom Tromey
2020-08-30 19:18 ` Tom Tromey
2020-08-31 17:09   ` Tom Tromey
2020-08-31 21:39     ` Simon Marchi
2020-09-01 14:23       ` Tom Tromey
2020-09-01 14:28         ` Simon Marchi
2020-10-17 22:33       ` Tom Tromey
2020-09-01 13:24     ` Simon Marchi
2020-09-01 14:20       ` Tom Tromey
2020-09-01 14:30         ` Simon Marchi
2020-09-01 14:41     ` Simon Marchi [this message]
2020-09-01 17:59       ` Tom Tromey
2020-10-17 20:17     ` 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=74b64278-9789-9130-13fb-c722b06c09a9@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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