Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Simon Marchi (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Andrew Burgess <andrew.burgess@embecosm.com>,	gdb-patches@sourceware.org
Subject: [review] gdb: Split global symbol search into separate functions
Date: Mon, 02 Dec 2019 19:42:00 -0000	[thread overview]
Message-ID: <20191202194216.EA06E2816F@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1575314132000.I06b26920f35c268f7a38d8203dc2c2813aa501c6@gnutoolchain-gerrit.osci.io>

Simon Marchi has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/738
......................................................................


Patch Set 1:

(1 comment)

| --- gdb/symtab.c
| +++ gdb/symtab.c
| @@ -4597,17 +4714,4 @@ global_symbol_searcher::search () const
| -			     .symbol == NULL))
| -			found_misc = 1;
| -		    }
| -		}
| -	    }
| -	}
| -    }
| -
| +  bool found_msymbol = false;
| +  std::set<symbol_search> result_set;

PS1, Line 4715:

Maybe a bit pedantic, but introducing the set in this patch does
possibly change the behavior, doesn't it?  Wouldn't it be better to
keep appending to a vector, as before, and then replace the vector
with a set in the following patch, with a justification of why that
change is needed?

|    for (objfile *objfile : current_program_space->objfiles ())
|      {
| -      for (compunit_symtab *cust : objfile->compunits ())
| -	{
| -	  bv = COMPUNIT_BLOCKVECTOR (cust);
| -	  for (i = GLOBAL_BLOCK; i <= STATIC_BLOCK; i++)
| -	    {
| -	      b = BLOCKVECTOR_BLOCK (bv, i);
| -	      ALL_BLOCK_SYMBOLS (b, iter, sym)

-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I06b26920f35c268f7a38d8203dc2c2813aa501c6
Gerrit-Change-Number: 738
Gerrit-PatchSet: 1
Gerrit-Owner: Andrew Burgess <andrew.burgess@embecosm.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Mon, 02 Dec 2019 19:42:16 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment


  reply	other threads:[~2019-12-02 19:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 19:15 Andrew Burgess (Code Review)
2019-12-02 19:42 ` Simon Marchi (Code Review) [this message]
2019-12-02 23:44 ` [review v2] " Andrew Burgess (Code Review)
2019-12-02 23:44 ` Andrew Burgess (Code Review)
2019-12-03  2:18 ` Simon Marchi (Code Review)
2019-12-03 10:56 ` [review v4] " Andrew Burgess (Code Review)
2019-12-03 16:38 ` Simon Marchi (Code Review)
2019-12-04 10:49 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-04 10:49 ` Sourceware to Gerrit sync (Code Review)

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=20191202194216.EA06E2816F@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gnutoolchain-gerrit@osci.io \
    /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