Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa] Deprecate msymbol.info, add msymbol.bfd_symbol?
Date: Sat, 11 Oct 2003 17:16:00 -0000	[thread overview]
Message-ID: <3F883ABD.3080504@redhat.com> (raw)

There isn't yet a patch yet.  I wan't to run the theory past people, 
especially the symtab maintainers.

A recent thread discussed the "info" field of the symbol table where 
MichaelC was trying to pack it down, while I was arguing that it should 
"just go", instead have the computation performed by 
MAKE_MSYMBOL_SPECIAL on every minimal-symbol performed on-demand (and 
after the symbo-table load).

The problem with eliminating "info" is that it would leave the on-demand 
code with no efficient way to find the underlying BFD info that it 
needes :-(

Consequently, I'd like to propose that "info" be superseeded by a 
"struct bfd_symbol *" pointer.

I say "superseed" as I'd prefer doing this in two steps.  In addition to 
the per-architecture MAKE_MSYMBOL_SPECIAL, readers like elfread.c also 
squirrel away info in that field :-/

The consequence will be that, for a time, the minimal symbol table will 
be bigger.  Since its the minimal-symbol table I don't feel too guilty, 
long term the minimal-symbol's size will be restored.  In fact, given 
the apparent overlap between bfd_symbol and general_symbol_info (name, 
section, bfd_section, ?), it opens the way to further savings.

thoughts? does the theory look correct?
Andrew


             reply	other threads:[~2003-10-11 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11 17:16 Andrew Cagney [this message]
2003-10-11 18:39 Michael Elizabeth Chastain
2003-10-11 20:02 ` Andrew Cagney
2003-10-13 20:28   ` Elena Zannoni
2003-10-11 20:22 Michael Elizabeth Chastain
2003-10-11 20:42 ` Andrew Cagney
2003-10-11 20:44 Michael Elizabeth Chastain
2003-10-14 17:36 Michael Elizabeth Chastain
2003-10-14 20:09 ` Elena Zannoni

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=3F883ABD.3080504@redhat.com \
    --to=ac131313@redhat.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