From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Remove some symtab accessors
Date: Wed, 6 Apr 2022 10:42:01 -0400 [thread overview]
Message-ID: <20220406144205.1415376-1-simon.marchi@polymtl.ca> (raw)
I am playing with symtabs currently and was a bit confused with some
accessors that make some things appear as if they are symtab-specific,
when they are not. These accessors forward to the symtab's parent
objects. I don't think they are very useful and just hide the real
object structure of GDB, so I suggest removing them.
Simon Marchi (4):
gdb: remove symtab::dirname
gdb: remove symtab::blockvector
gdb: remove symtab::objfile
gdb: remove symtab::pspace
gdb/ada-exp.y | 3 +-
gdb/ada-lang.c | 8 ++--
gdb/annotate.c | 4 +-
gdb/breakpoint.c | 9 +++--
gdb/c-exp.y | 5 ++-
gdb/cli/cli-cmds.c | 8 ++--
gdb/coffread.c | 2 +-
gdb/compile/compile-object-load.c | 2 +-
gdb/compile/compile.c | 2 +-
gdb/guile/scm-symtab.c | 12 +++---
gdb/linespec.c | 63 ++++++++++++++++++-------------
gdb/mdebugread.c | 16 ++++----
gdb/mi/mi-symbol-cmds.c | 2 +-
gdb/objfiles.c | 2 +-
gdb/p-exp.y | 5 ++-
gdb/parse.c | 2 +-
gdb/python/py-symtab.c | 24 ++++++------
gdb/source-cache.c | 5 ++-
gdb/source.c | 19 +++++-----
gdb/symmisc.c | 10 ++---
gdb/symtab.c | 14 ++-----
gdb/symtab.h | 26 -------------
gdb/tui/tui-source.c | 2 +-
gdb/tui/tui-winsource.c | 2 +-
24 files changed, 116 insertions(+), 131 deletions(-)
base-commit: 7fb56b98937a2feef5a3e12d8b00506ff4d132be
--
2.35.1
next reply other threads:[~2022-04-06 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:42 Simon Marchi [this message]
2022-04-06 14:42 ` [PATCH 1/4] gdb: remove symtab::dirname Simon Marchi
2022-04-06 14:42 ` [PATCH 2/4] gdb: remove symtab::blockvector Simon Marchi
2022-04-06 14:42 ` [PATCH 3/4] gdb: remove symtab::objfile Simon Marchi
2022-04-06 14:42 ` [PATCH 4/4] gdb: remove symtab::pspace Simon Marchi
2022-04-07 14:08 ` [PATCH 0/4] Remove some symtab accessors Tom Tromey
2022-04-07 17:08 ` Simon Marchi
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=20220406144205.1415376-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).