public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Update partial_symtab comment
Date: Thu, 05 Mar 2020 12:39:00 -0000	[thread overview]
Message-ID: <d4d947ae37f84bb01eac7de69d0e363e608d0821@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT d4d947ae37f84bb01eac7de69d0e363e608d0821 ***

commit d4d947ae37f84bb01eac7de69d0e363e608d0821
Author:     Tom Tromey <tom@tromey.com>
AuthorDate: Fri Feb 21 14:44:41 2020 -0700
Commit:     Tom Tromey <tom@tromey.com>
CommitDate: 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 --git a/gdb/ChangeLog b/gdb/ChangeLog
index 6ac818b04d..782f6008c3 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 1b1f57cf76..0effedc4ec 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-03-05 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 12:39 gdb-buildbot [this message]
2020-03-05 12:56 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-03-05 12:57 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-03-05 13:00 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-03-05 13:37 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-03-05 14:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-03-05 15:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-03-06 13:55 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-03-07 22:45 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot

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=d4d947ae37f84bb01eac7de69d0e363e608d0821@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).