Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Deprecate msymbol.info, add msymbol.bfd_symbol?
Date: Sat, 11 Oct 2003 20:02:00 -0000	[thread overview]
Message-ID: <3F8861D6.7080302@redhat.com> (raw)
In-Reply-To: <200310111839.h9BIdNm8020908@duracef.shout.net>


> The first meaning can die as soon as someone can test a coff platform
> with a trivial patch to coffread.c.
> 
> The second meaning is: dbxread.c stores the size of the msym
> in 'msymbol.info'.  It does this in case SOFUN_ADDRESS_MAYBE_MISSING
> is set, in order to synthesize texthigh for that file.
> 
> The third meaning is that arm-tdep.c, m68hc11-tdep.c, mips-tdep.c,
> and sh-tdep.c use msymbol.info as a place to store one or two
> flag bits.

The third meaning needs to be refined slightly.  MAKE_MSYMBOL_SPECIAL, 
for coff, doesn't yet take a "bfd_symbol", in fact, coffread doesn't 
even use BFD's canonicalize_symtab to read the symbols.

>> Consequently, I'd like to propose that "info" be superseeded by a 
>> "struct bfd_symbol *" pointer.
> 
> 
> I don't quite understand your proposal, because there are three
> meanings of "msymbol.info".  Which meanings do you want to supersede?
> Can you put up a little sample code?

If I ignore coff, Arm's arm_pc_is_thumb would look like:

	sym = lookup_minimal_symbol_by_pc (memaddr);
	if (sym && sym->bfd_symbol is "elf like")
	  return (ELF_ST_TYPE (((elf_symbol_type *) 
(sym->bfd_symbol))->internal_elf_sym.st_info) == STT_LOPROC)
	else
	  return 0;

MIPS would be identical.  The existing MAKE_MSYMBOL_SPECIAL wouldn't be 
needed.

The other ELF use in elfread + dbxread:

               /* Pass symbol size field in via BFD.  FIXME!!!  */
               size = ((elf_symbol_type *) sym)->internal_elf_sym.st_size;
               msym = record_minimal_symbol_and_info
                 ((char *) sym->name, symaddr,
                  ms_type, (void *) size, sym->section, objfile);

(having calls to record_minimal_symbol_and_info with a NULL info sux :-) 
could be addressed similar.  Anyone realise that the code assumes elf?

>> The consequence will be that, for a time, the minimal symbol table will 
>> be bigger.
> 
> 
> Here are some numbers from some old test run:
> 
>   msym  0.3 mb
>   psym 11.9 mb
>   sym  30.1 mb
>   mt    8.7 mb  # main_type
> 
> The msym's are not space critical.

Yes, I was secretly assuming that.

> It sucks that msymbol.info is overloaded for three different meanings
> (and none of them is a pointer so we get all those nasty casts).  Let's
> separate it into different fields, and then when the data types are
> nice and correct, if we want the space back (which I think we won't),
> then we can go for 'union' and bit-field things to get the size back
> down.

This could immediatly eliminate two of them.  I think the coff version 
of ARM could also be eliminated if coffread (yea, right ... :-) fully 
utilized BFD.

Andrew



  reply	other threads:[~2003-10-11 20:02 UTC|newest]

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

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=3F8861D6.7080302@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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