public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Update partial_symtab comment
Date: Fri, 21 Feb 2020 21:54:00 -0000	[thread overview]
Message-ID: <20200221215403.17032.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d4d947ae37f84bb01eac7de69d0e363e608d0821

commit d4d947ae37f84bb01eac7de69d0e363e608d0821
Author: Tom Tromey <tom@tromey.com>
Date:   Fri Feb 21 14:44:41 2020 -0700

    Update partial_symtab comment
    
    The introductory comment for partial_symtab has been mildly incorrect
    since the partial symtab code was changed to allocate partial symtabs
    with "new".  This patch removes the incorrect text.
    
    gdb/ChangeLog
    2020-02-21  Tom Tromey  <tom@tromey.com>
    
    	* psympriv.h (struct partial_symtab): Update comment.

Diff:
---
 gdb/ChangeLog  | 4 ++++
 gdb/psympriv.h | 3 +--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 6ac818b..782f600 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-02-21  Tom Tromey  <tom@tromey.com>
+
+	* psympriv.h (struct partial_symtab): Update comment.
+
 2020-02-21  Tom Tromey  <tromey@adacore.com>
 
 	* mips-tdep.h (mips_pc_is_mips16, mips_pc_is_micromips): Parameter
diff --git a/gdb/psympriv.h b/gdb/psympriv.h
index 1b1f57c..0effedc 100644
--- a/gdb/psympriv.h
+++ b/gdb/psympriv.h
@@ -99,8 +99,7 @@ enum psymtab_search_status
    They are all chained on partial symtab lists.
 
    Even after the source file has been read into a symtab, the
-   partial_symtab remains around.  They are allocated on an obstack,
-   objfile_obstack.  */
+   partial_symtab remains around.  */
 
 struct partial_symtab
 {


                 reply	other threads:[~2020-02-21 21:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200221215403.17032.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@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).