From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Elena Zannoni <ezannoni@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [rfa] symbol hashing, part 2/n - ALL_BLOCK_SYMBOLS
Date: Thu, 11 Oct 2001 18:06:00 -0000 [thread overview]
Message-ID: <3BC64216.3040308@cygnus.com> (raw)
In-Reply-To: <B6F9988E-BEAA-11D5-BCD0-0030657B5340@cgsoftware.com>
> Your second commit is this new (ULGH) macro. The macro (ULGH) shouldn't break anything but it is however still a (ULGH) macro. Just include the extra tweeks you found.
>
> (If you haven't figured it out, breakpoint.h has a similar (ULGH) macro so I'm biteing my tongue on this change [:-)]
>
> Unfortunately, it can't be done without a macro here, without introducing about 30 new functions, spread out across a whole bunch of files.
> The real problem is so many things feel an uncontrollable urge to walk an entire block (or the entire symbol table).
Yes, like I said, I'm biteing my tongue :-)
Andrew
next prev parent reply other threads:[~2001-10-11 18:06 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
2001-10-11 16:55 ` Daniel Jacobowitz
2001-10-11 17:43 ` Andrew Cagney
2001-10-11 17:48 ` Daniel Berlin
2001-10-11 18:06 ` Andrew Cagney [this message]
2001-10-11 17:48 ` Daniel Jacobowitz
2001-10-11 18:18 ` Andrew Cagney
2001-10-12 9:08 ` Elena Zannoni
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=3BC64216.3040308@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dan@cgsoftware.com \
--cc=drow@mvista.com \
--cc=ezannoni@cygnus.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