Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfa] symbol hashing, part 2/n - ALL_BLOCK_SYMBOLS
Date: Thu, 11 Oct 2001 16:52:00 -0000	[thread overview]
Message-ID: <15302.12883.577991.796942@krustylu.cygnus.com> (raw)
In-Reply-To: <5201EEBC-BEA2-11D5-A4DE-0030657B5340@cgsoftware.com>

Daniel Berlin writes:
 > 
 > On Thursday, October 11, 2001, at 07:46  PM, Elena Zannoni wrote:
 > 
 > >
 > > Daniel,
 > > Thanks so much for doing this. It makes it so much easier.
 > >
 > > Yes, I looked ths over and it seems to work, except that I would really
 > > prefer the change to printcmd.c split in two. The first bit to
 > > rationalize that "if (func)..."  code. This would have with it all
 > > the indentation changes as well. The code as it is now doesn't really
 > > make much sense. So, that looks a good change to me. But it has nothing
 > > to do with the new macro.  After that change is in, you can introduce
 > > the macro in printcmd.c w/o having all the indent changes.
 > > It also makes it easier to distinguish a no-op change (the macro) from
 > > the other one.
 > >
 > > The cahnge is printcmd.c needs to delete also the
 > > 	  sym = BLOCK_SYM (b, i);
 > > line.
 > >
 > > [Note that I don't maintain printcmd.c, so, I should just shut up :-)]
 > >
 > > I applied your patch as is to my sources, and did a grep for BLOCK_SYM,
 > > and found a few more for loops that could be converted:
 > >
 > >
 > > This one in buildsym.c:
 > > line ~280:
 > >
 > > 	  struct symbol *sym;
 > > 	  for (i = 0; i < BLOCK_NSYMS (block); i++)
 > > 	    {
 > > 	      sym = BLOCK_SYM (block, i);
 > >
 > > And this one in symtab.c:
 > > line ~1500:
 > >
 > > 	top = BLOCK_NSYMS (block);
 > > 	for (bot = 0; bot < top; bot++)
 > > 	  {
 > > 	    sym = BLOCK_SYM (block, bot);
 > >
 > 
 > Both of these loops get changed by the next patch i'm sure he'll submit, 
 > to introduce hashed blocks, which is probably why he didn't change them.

Ok, thanks!

Elena


  reply	other threads:[~2001-10-11 16:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09  9:35 Daniel Jacobowitz
2001-10-11 16:39 ` Elena Zannoni
2001-10-11 16:48   ` Daniel Berlin
2001-10-11 16:52     ` Elena Zannoni [this message]
2001-10-11 16:55   ` Daniel Jacobowitz
2001-10-11 17:43     ` Andrew Cagney
2001-10-11 17:48       ` Daniel Jacobowitz
2001-10-11 18:18         ` Andrew Cagney
2001-10-12  9:08         ` Elena Zannoni
2001-10-11 17:48       ` Daniel Berlin
2001-10-11 18:06         ` Andrew Cagney
2001-10-12  9:05       ` Elena Zannoni
2001-10-11 18:05     ` Daniel Jacobowitz
2001-10-12  9:09       ` Elena Zannoni
2001-10-12 10:17         ` Daniel Jacobowitz
2001-10-12  8:49     ` Elena Zannoni
2001-10-12 11:59       ` Daniel Jacobowitz
2001-10-12 13:03         ` Andrew Cagney
2001-10-12 15:34         ` Elena Zannoni
2001-10-12 16:53         ` Daniel Jacobowitz

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=15302.12883.577991.796942@krustylu.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=dan@cgsoftware.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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