public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <xdje42@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Buildsym cleanups: more docs, more uniform set-up and tear-down
Date: Mon, 15 Dec 2014 03:44:00 -0000	[thread overview]
Message-ID: <871to1vapo.fsf@codesourcery.com> (raw)
In-Reply-To: <m3a92rhyu0.fsf@seba.sebabeach.org> (Doug Evans's message of	"Sat, 13 Dec 2014 16:14:31 -0800")

Doug Evans <xdje42@gmail.com> writes:

Some comments on indentation.

>  /* Restart compilation for a symtab.
> +   CUST is the result of end_expandable_symtab.
> +   NAME,START_ADDR are the source file we are resuming with.

Space after comma is missing.

>  
>  /* Subroutine of end_symtab_from_static_block to simplify it.
>     Handle the "no blockvector" case.
> -   When this happens there is nothing to record, so just free up
> -   any memory we allocated while reading debug info.  */
> +   When this happens there is nothing to record, so there's nothing to do:
> +   memory will be freed up later.
> +   This function is kept to have a place to document the issues.  */
>  
>  static void
>  end_symtab_without_blockvector (void)
>  {
> -  /* Free up all the subfiles.
> -     We won't be adding a compunit to the objfile's list of compunits,
> +  /* Note: We won't be adding a compunit to the objfile's list of compunits,
>       so there's nothing to unchain.  However, since each symtab
>       is added to the objfile's obstack we can't free that space.
>       We could do better, but this is believed to be a sufficiently rare
>       event.  */
> -  free_buildsym_compunit ();
>  }

end_symtab_without_blockvector is empty, so remove it?

-- 
Yao (齐尧)

  reply	other threads:[~2014-12-15  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14  0:15 Doug Evans
2014-12-15  3:44 ` Yao Qi [this message]
2014-12-17  8:06   ` Doug Evans

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=871to1vapo.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).