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:28:17 -0400	[thread overview]
Message-ID: <6617d4e8-ecc6-976b-56aa-9002372e76ec@simark.ca> (raw)
In-Reply-To: <87k0xd7f04.fsf@tromey.com>

On 2020-09-01 10:23 a.m., Tom Tromey wrote:
> Simon> I think it would be a good time to get rid of the objfile
> Simon> parameter in the add_psymbol methods.  This parameter shouldn't
> Simon> be there if the partial symtabs are really objfile-independent.
> 
> Yeah.  I have another patch to remove it from end_psymtab_common, but I
> didn't look at removing it from the add_psymbol methods.
> 
> I think it's a good idea, but it might be a pain to pipe the object
> everywhere it is needed.  So I'd prefer to do this as a separate patch.

I have toyed with it and I agree.  It's more of a long term goal and there
are a few little annoying dependencies to remove.  So, not for this patch
indeed.

> Simon> The other use of objfile in partial_symtab::add_psymbol is for
> Simon> stats.  I think that could be easily implemented some other way
> Simon> that doesn't require passing the objfile.
> 
> I feel like the stats are not very useful and could just be removed.  I
> have never once used them; the bcache already tracks its own efficiency;
> and gdb already knows how many psymbols actually exist.

I agree.

Simon


  reply	other threads:[~2020-09-01 14:28 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 [this message]
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
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=6617d4e8-ecc6-976b-56aa-9002372e76ec@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