Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Richard Bunt <Richard.Bunt@arm.com>,
	Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/7] Fortran info types, info modules, info module ...
Date: Sat, 27 Jul 2019 16:22:00 -0000	[thread overview]
Message-ID: <cover.1564243858.git.andrew.burgess@embecosm.com> (raw)

A set of patches working toward the goal of adding some new commands
related to Fortran modules.

  #1 - Not Fortran related at all, just adds a new flag to the "info
       functions" and "info variables" commands.

  #2 - In preparation for patch #3.

  #3 - Ensure Fortran variables from modules show up in "info
       variables" output.

  #4 - Fix "info types" for Fortran.

  #5 - We create a symbol for each Fortran module, don't show this in
       the "info types" output.

  #6 - New command "info modules", list all Fortran modules.

  #7 - Two new commands "info module functions" and "info module
       variables", these are like "info functions" and "info variables",
       but with a module twist.

Thanks,
Andrew

---

Andrew Burgess (7):
  gdb: Add new -n flag to some info commands
  gdb: Add an is_declaration field to each symbol
  gdb/fortran: Include module variables in 'info variables' output
  gdb/fortran: Implement la_print_typedef for Fortran
  gdb/fortran: Don't include module symbols when searching for types
  gdb/fortran: Add new 'info modules' command
  gdb: Add new commands to list module variables and functions

 gdb/ChangeLog                              |  90 ++++++
 gdb/NEWS                                   |  24 ++
 gdb/cli/cli-utils.c                        |  65 +---
 gdb/cli/cli-utils.h                        |  39 +--
 gdb/doc/ChangeLog                          |  14 +
 gdb/doc/gdb.texinfo                        |  66 +++-
 gdb/dwarf2read.c                           |  11 +
 gdb/f-lang.c                               |   2 +-
 gdb/f-lang.h                               |   5 +
 gdb/f-typeprint.c                          |  11 +
 gdb/psymtab.c                              |   2 +
 gdb/python/python.c                        |   4 +-
 gdb/stack.c                                |  77 ++++-
 gdb/symtab.c                               | 471 +++++++++++++++++++++++++++--
 gdb/symtab.h                               |  12 +-
 gdb/testsuite/ChangeLog                    |  39 +++
 gdb/testsuite/gdb.base/info-fun.exp        |  97 +++---
 gdb/testsuite/gdb.base/info-var-f1.c       |  24 ++
 gdb/testsuite/gdb.base/info-var-f2.c       |  26 ++
 gdb/testsuite/gdb.base/info-var.exp        |  60 ++++
 gdb/testsuite/gdb.base/info-var.h          |  18 ++
 gdb/testsuite/gdb.fortran/info-modules.exp | 180 +++++++++++
 gdb/testsuite/gdb.fortran/info-types.exp   |  49 +++
 gdb/testsuite/gdb.fortran/info-types.f90   |  72 +++++
 gdb/testsuite/gdb.fortran/module.exp       |  24 ++
 gdb/testsuite/lib/fortran.exp              |  12 +
 26 files changed, 1323 insertions(+), 171 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/info-var-f1.c
 create mode 100644 gdb/testsuite/gdb.base/info-var-f2.c
 create mode 100644 gdb/testsuite/gdb.base/info-var.exp
 create mode 100644 gdb/testsuite/gdb.base/info-var.h
 create mode 100644 gdb/testsuite/gdb.fortran/info-modules.exp
 create mode 100644 gdb/testsuite/gdb.fortran/info-types.exp
 create mode 100644 gdb/testsuite/gdb.fortran/info-types.f90

-- 
2.14.5


             reply	other threads:[~2019-07-27 16:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 16:22 Andrew Burgess [this message]
2019-07-27 16:22 ` [PATCH 2/7] gdb: Add an is_declaration field to each symbol Andrew Burgess
2019-07-29 20:21   ` Tom Tromey
2019-07-30 21:00     ` Andrew Burgess
2019-07-27 16:22 ` [PATCH 3/7] gdb/fortran: Include module variables in 'info variables' output Andrew Burgess
2019-07-27 16:23 ` [PATCH 5/7] gdb/fortran: Don't include module symbols when searching for types Andrew Burgess
2019-08-28 12:37   ` Andrew Burgess
2019-08-29  9:09     ` Tom de Vries
2019-08-29 11:45       ` Tom de Vries
2019-08-29 12:47     ` [committed][gdb/testsuite] Fix gdb.fortran/info-types.exp regexp Tom de Vries
2019-07-27 16:23 ` [PATCH 6/7] gdb/fortran: Add new 'info modules' command Andrew Burgess
2019-07-27 16:45   ` Eli Zaretskii
2019-07-29 20:30   ` Tom Tromey
2019-07-27 16:23 ` [PATCH 1/7] gdb: Add new -n flag to some info commands Andrew Burgess
2019-07-27 16:41   ` Eli Zaretskii
2019-07-30 21:02     ` Andrew Burgess
2019-07-31 14:51       ` Eli Zaretskii
2019-08-26 15:52         ` Andrew Burgess
2019-08-26 16:19           ` Eli Zaretskii
2019-08-27 15:27             ` Andrew Burgess
2019-08-28 15:13               ` [committed][gdb/testsuite] Fix info-var.exp for debug info from other files Tom de Vries
2019-07-29 20:23   ` [PATCH 1/7] gdb: Add new -n flag to some info commands Tom Tromey
2019-07-27 16:23 ` [PATCH 7/7] gdb: Add new commands to list module variables and functions Andrew Burgess
2019-07-27 17:06   ` Eli Zaretskii
2019-07-27 16:23 ` [PATCH 4/7] gdb/fortran: Implement la_print_typedef for Fortran Andrew Burgess
2019-08-28 12:37   ` Andrew Burgess

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=cover.1564243858.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=Richard.Bunt@arm.com \
    --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