Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Cagney <cagney@gnu.org>,
	Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add SYMBOL_SET_LINKAGE_NAME
Date: Tue, 17 Feb 2004 19:14:00 -0000	[thread overview]
Message-ID: <16434.26365.373673.881423@localhost.redhat.com> (raw)
In-Reply-To: <20040217160126.GA29934@nevyn.them.org>

Daniel Jacobowitz writes:
 > Because the cleaner interface is not my goal - it's a side goal to my
 > actual aims, which are improved GDB startup time and memory usage. 

From your previous postings I understand is that your cplusplus stuff
has a noticeable impact on performance and memory usage and you are
trying to shave gdb's time and size wherever there is a chance. From
Paul's postings instead I get the impression that he needs to revise
the current interface.

You are saying that you are not willing to take a step back and look
at things from a broader perspective.  I sincerely hope I
misunderstood your statement.

The symbol table is already a mess, with multiple redundant
interfaces.  At the moment there isn't a clear picture of what various
bits of gdb need from the symbol table.  How do we know the direction
we are going is improving things generally across the board?  How can
we know that, if this is not the case, the impact is not too heavy on
other parts and we can live with the tradeoff?

I am not saying that we have to know everything in minutious details
before we can touch the code (that's very likely totally unfeasible),
but at least, have an understanding of the big picture and the
consequences.



  reply	other threads:[~2004-02-17 19:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 21:24 Daniel Jacobowitz
2004-02-16 21:53 ` Elena Zannoni
2004-02-16 22:57   ` Daniel Jacobowitz
2004-02-16 23:35     ` Paul Hilfinger
2004-02-17  0:05       ` Daniel Jacobowitz
2004-02-17  9:59         ` Paul N. Hilfinger
2004-02-17 15:57     ` Andrew Cagney
2004-02-17 16:01       ` Daniel Jacobowitz
2004-02-17 19:14         ` Elena Zannoni [this message]
2004-02-17 19:29           ` Daniel Jacobowitz
2004-02-17 23:10             ` Andrew Cagney
2004-02-18  0:43             ` Elena Zannoni
2004-02-18  1:04               ` Daniel Jacobowitz
2004-02-18  0:20 ` David Carlton
2004-02-18  0:23   ` Daniel Jacobowitz
2004-02-18  0:27     ` Elena Zannoni
2004-02-18  0:32       ` Daniel Jacobowitz
2004-02-18  0:54         ` Elena Zannoni
2004-02-18  1:06           ` Daniel Jacobowitz
2004-02-18  0:49   ` Paul Hilfinger
2004-02-18  1:27     ` David Carlton
2004-02-18  8:12       ` Paul N. Hilfinger
2004-02-18 16:45         ` David Carlton
2004-02-20  9:32           ` Paul N. Hilfinger

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=16434.26365.373673.881423@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --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