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] Make symtab members private Date: Mon, 24 Jun 2024 15:28:30 +0000 (GMT) [thread overview] Message-ID: <20240624152830.B1FB33858432@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=440897605540c0703c29a84450ab3e5eccda91bd commit 440897605540c0703c29a84450ab3e5eccda91bd Author: Tom Tromey <tromey@adacore.com> Date: Wed Jun 5 08:55:21 2024 -0600 Make symtab members private This rearranges symtab so that the private members appear at the end, and then adds the "private" keyword. Diff: --- gdb/symtab.h | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/gdb/symtab.h b/gdb/symtab.h index e75c6389953..19bb697a5a1 100644 --- a/gdb/symtab.h +++ b/gdb/symtab.h @@ -1765,15 +1765,6 @@ struct symtab struct symtab *next; - /* Backlink to containing compunit symtab. */ - - struct compunit_symtab *m_compunit; - - /* Table mapping core addresses to line numbers for this file. - Can be NULL if none. Never shared between different symtabs. */ - - const struct linetable *m_linetable; - /* Name of this source file, in a form appropriate to print to the user. This pointer is never nullptr. */ @@ -1790,6 +1781,17 @@ struct symtab This pointer is never nullptr.*/ const char *filename_for_id; +private: + + /* Backlink to containing compunit symtab. */ + + struct compunit_symtab *m_compunit; + + /* Table mapping core addresses to line numbers for this file. + Can be NULL if none. Never shared between different symtabs. */ + + const struct linetable *m_linetable; + /* Language of this source file. */ enum language m_language;
reply other threads:[~2024-06-24 15:28 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=20240624152830.B1FB33858432@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: linkBe 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).