public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Replace SYMBOL_SET_LINKAGE_NAME with a member function
Date: Wed, 27 Nov 2019 03:54:00 -0000	[thread overview]
Message-ID: <38f6c8b4-25d7-b116-9fe1-b87dfc393b5d@simark.ca> (raw)
In-Reply-To: <20191126204351.83076-1-cbiesinger@google.com>

On 2019-11-26 3:43 p.m., Christian Biesinger via gdb-patches wrote:
> Easier to read, shorter, and will later make it possible to make the
> name field private.

Thanks, LGTM, with the nits below fixed.

> diff --git a/gdb/stabsread.c b/gdb/stabsread.c
> index 6ec9f971e1..3f3f0a624f 100644
> --- a/gdb/stabsread.c
> +++ b/gdb/stabsread.c
> @@ -399,8 +399,7 @@ patch_block_stabs (struct pending *symbols, struct pending_stabs *stabs,
>        /* for all the stab entries, find their corresponding symbols and 
>           patch their types!  */
>  
> -      for (ii = 0; ii < stabs->count; ++ii)
> -	{
> +      for (ii = 0; ii < stabs->count; ++ii) {

Unrelated change.

> diff --git a/gdb/symtab.h b/gdb/symtab.h
> index 897ffda76e..ff51069b6c 100644
> --- a/gdb/symtab.h
> +++ b/gdb/symtab.h
> @@ -407,8 +407,7 @@ struct general_symbol_info
>  
>    /* Return the demangled name for a symbol based on the language for
>       that symbol.  If no demangled name exists, return NULL.  */
> -  const char *demangled_name () const;
> -
> +  const char *demangled_name () const; 

Unrelated change.

Simon

  reply	other threads:[~2019-11-27  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 20:43 Christian Biesinger via gdb-patches
2019-11-27  3:54 ` Simon Marchi [this message]
2019-11-27 17:10   ` Christian Biesinger via gdb-patches

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=38f6c8b4-25d7-b116-9fe1-b87dfc393b5d@simark.ca \
    --to=simark@simark.ca \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).