public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* [PATCH 0/7] location -> location spec
@ 2022-05-27 18:02 Pedro Alves
  2022-05-27 18:02 ` [PATCH 1/7] event_location -> location_spec Pedro Alves
                   ` (7 more replies)
  0 siblings, 8 replies; 14+ messages in thread
From: Pedro Alves @ 2022-05-27 18:02 UTC (permalink / raw)
  To: gdb-patches

Currently, GDB internally uses the term "location" for both the
location specification the user had input, and for actual resolved
locations, like the breakpoint locations, or the result of decoding a
location spec to SaLs.  This is expecially confusing in the
breakpoints module.

For the location spec, we currently have struct "event_location", and
even the "event" part is misnamed.

This series everything related to location specifications from
"location" to "location spec".  event_location is renamed to
location_spec.  And then cleans up location_spec and its subclasses.

Tested on x86_64 GNU/Linux.

Pedro Alves (7):
  event_location -> location_spec
  Eliminate the two-level data structures behind location_specs
  Eliminate copy_location_spec
  Convert location_spec_empty_p to a method
  Convert location_spec_type to a method
  Convert location_spec_to_string to a method
  Convert set_location_spec_string to a method

 gdb/ada-lang.c                   |   4 +-
 gdb/ax-gdb.c                     |   6 +-
 gdb/break-catch-throw.c          |  17 +-
 gdb/breakpoint.c                 | 367 +++++++++--------
 gdb/breakpoint.h                 |  62 +--
 gdb/cli/cli-cmds.c               |  32 +-
 gdb/completer.c                  |  42 +-
 gdb/elfread.c                    |   3 +-
 gdb/guile/scm-breakpoint.c       |  21 +-
 gdb/linespec.c                   | 157 ++++----
 gdb/linespec.h                   |  12 +-
 gdb/location.c                   | 662 ++++++++++++-------------------
 gdb/location.h                   | 359 ++++++++++-------
 gdb/mi/mi-cmd-break.c            |  35 +-
 gdb/probe.c                      |   8 +-
 gdb/probe.h                      |   4 +-
 gdb/python/py-breakpoint.c       |  39 +-
 gdb/python/py-finishbreakpoint.c |   6 +-
 gdb/python/python.c              |  10 +-
 gdb/remote.c                     |   6 +-
 gdb/tracepoint.c                 |   6 +-
 21 files changed, 877 insertions(+), 981 deletions(-)


base-commit: 509e6230915a050d510a36ca9482193c76a6a216
-- 
2.36.0


^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2022-06-17  9:24 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-27 18:02 [PATCH 0/7] location -> location spec Pedro Alves
2022-05-27 18:02 ` [PATCH 1/7] event_location -> location_spec Pedro Alves
2022-05-28 10:08   ` Philippe Waroquiers
2022-05-30 15:02     ` Pedro Alves
2022-05-27 18:02 ` [PATCH 2/7] Eliminate the two-level data structures behind location_specs Pedro Alves
2022-05-30 15:09   ` Pedro Alves
2022-05-27 18:02 ` [PATCH 3/7] Eliminate copy_location_spec Pedro Alves
2022-05-27 18:02 ` [PATCH 4/7] Convert location_spec_empty_p to a method Pedro Alves
2022-05-27 18:02 ` [PATCH 5/7] Convert location_spec_type " Pedro Alves
2022-05-27 18:02 ` [PATCH 6/7] Convert location_spec_to_string " Pedro Alves
2022-05-27 18:02 ` [PATCH 7/7] Convert set_location_spec_string " Pedro Alves
2022-05-30 15:20   ` Pedro Alves
2022-06-15 19:47 ` [PATCH 0/7] location -> location spec Tom Tromey
2022-06-17  9:24   ` Pedro Alves

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).