Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] minsyms.c: Fix switching to GNU v3 ABI
Date: Thu, 25 Mar 2004 20:44:00 -0000	[thread overview]
Message-ID: <vt21xngu06b.fsf@zenia.home> (raw)
In-Reply-To: <20040310182259.GT25204@cygbert.vinschen.de>


This looks good.

One comment: I notice that we actually remove the leading character
earlier in prim_record_minimal_symbol_and_info, to check if the name
is the same as that of the GCC compilation marker symbol.  It would be
nicer if we could just remove the leading character once, at the top
of the function, and then simplify the the "__gnu_compiled" test.
Doing so shouldn't interfere with the GCC_COMPILED_FLAG_SYMBOL tests,
since the code already presumes those both start with 'g'.

If that works, please commit.

Corinna Vinschen <vinschen@redhat.com> writes:

> On Mar 10 18:54, Corinna Vinschen wrote:
> > 	* minsyms.c (install_minimal_symbols): Move dropping leading
> > 	char from linkage name from here...
> > 	(prim_record_minimal_symbol_and_info): ...to here.
> 
> Corrected patch below.  I forgot to remove the now unused leading_char
> >From install_minimal_symbols.
> 
> Corinna
> 
> 
> Index: minsyms.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/minsyms.c,v
> retrieving revision 1.41
> diff -u -p -r1.41 minsyms.c
> --- minsyms.c	9 Feb 2004 19:13:46 -0000	1.41
> +++ minsyms.c	10 Mar 2004 18:20:36 -0000
> @@ -611,6 +611,8 @@ prim_record_minimal_symbol_and_info (con
>    msymbol = &msym_bunch->contents[msym_bunch_index];
>    SYMBOL_INIT_LANGUAGE_SPECIFIC (msymbol, language_unknown);
>    SYMBOL_LANGUAGE (msymbol) = language_auto;
> +  if (name[0] == get_symbol_leading_char (objfile->obfd))
> +    ++name;
>    SYMBOL_SET_NAMES (msymbol, (char *)name, strlen (name), objfile);
>  
>    SYMBOL_VALUE_ADDRESS (msymbol) = address;
> @@ -831,7 +833,6 @@ install_minimal_symbols (struct objfile 
>    struct msym_bunch *bunch;
>    struct minimal_symbol *msymbols;
>    int alloc_count;
> -  char leading_char;
>  
>    if (msym_count > 0)
>      {
> @@ -859,18 +860,11 @@ install_minimal_symbols (struct objfile 
>           each bunch is full. */
>  
>        mcount = objfile->minimal_symbol_count;
> -      leading_char = get_symbol_leading_char (objfile->obfd);
>  
>        for (bunch = msym_bunch; bunch != NULL; bunch = bunch->next)
>  	{
>  	  for (bindex = 0; bindex < msym_bunch_index; bindex++, mcount++)
> -	    {
> -	      msymbols[mcount] = bunch->contents[bindex];
> -	      if (SYMBOL_LINKAGE_NAME (&msymbols[mcount])[0] == leading_char)
> -		{
> -		  SYMBOL_LINKAGE_NAME (&msymbols[mcount])++;
> -		}
> -	    }
> +	    msymbols[mcount] = bunch->contents[bindex];
>  	  msym_bunch_index = BUNCH_SIZE;
>  	}
>  
> 
> -- 
> Corinna Vinschen
> Cygwin Developer
> Red Hat, Inc.


  parent reply	other threads:[~2004-03-25 20:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Corinna Vinschen
2004-03-10 10:57 ` Corinna Vinschen
2004-03-19  0:09 ` Jim Blandy
2004-03-10 15:04   ` Jim Blandy
2004-03-19  0:09 ` Daniel Jacobowitz
2004-03-10 15:08   ` Daniel Jacobowitz
2004-03-10 15:55   ` Corinna Vinschen
2004-03-10 16:04     ` Daniel Jacobowitz
2004-03-10 16:16       ` Corinna Vinschen
2004-03-19  0:09         ` Corinna Vinschen
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-10 16:20           ` Daniel Jacobowitz
2004-03-19  0:09           ` Corinna Vinschen
2004-03-10 16:34             ` Corinna Vinschen
2004-03-10 16:37             ` Daniel Jacobowitz
2004-03-10 17:54               ` Corinna Vinschen
2004-03-10 18:02                 ` David Carlton
2004-03-19  0:09                   ` David Carlton
2004-03-10 18:23                 ` Corinna Vinschen
2004-03-19  0:09                   ` Corinna Vinschen
2004-03-22 17:34                   ` Corinna Vinschen
2004-03-22 17:38                     ` Corinna Vinschen
2004-03-25 20:44                   ` Jim Blandy [this message]
2004-03-26 13:57                     ` Corinna Vinschen
2004-03-26 17:54                       ` Eli Zaretskii
2004-03-28 18:28                       ` Jim Blandy
2004-03-29 11:26                         ` Corinna Vinschen
2004-03-19  0:09                 ` Corinna Vinschen
2004-03-19  0:09                 ` Ian Lance Taylor
2004-03-10 18:30                   ` Ian Lance Taylor
2004-03-19  0:09                   ` Corinna Vinschen
2004-03-10 18:46                     ` Corinna Vinschen
2004-03-10 19:02                     ` Ian Lance Taylor
2004-03-19  0:09                       ` Ian Lance Taylor
2004-03-19  0:09                 ` Daniel Jacobowitz
2004-03-10 18:20                   ` Daniel Jacobowitz
2004-03-19  0:09               ` Daniel Jacobowitz
2004-03-10 16:43             ` Corinna Vinschen
2004-03-10 16:46               ` Daniel Jacobowitz
2004-03-19  0:09                 ` Daniel Jacobowitz
2004-03-19  0:09               ` Corinna Vinschen
2004-03-19  0:09       ` Daniel Jacobowitz
2004-03-19  0:09     ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2004-03-10 18:03 Michael Elizabeth Chastain
2004-03-19  0:09 ` Michael Elizabeth Chastain

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=vt21xngu06b.fsf@zenia.home \
    --to=jimb@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