Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCHv2 0/4] Fortran info types, info modules, info module ...
Date: Thu, 03 Oct 2019 11:29:00 -0000	[thread overview]
Message-ID: <cover.1570101531.git.andrew.burgess@embecosm.com> (raw)

This is a new version of the series I originally posted here:

   https://sourceware.org/ml/gdb-patches/2019-07/msg00608.html

From the original series patches #1, #4, and #5 have already been
merged, while patches #2 and #3 are no longer needed thanks to Tom's
recent copy relocation work.

In this series patches #1 and #2 are new, while patches #3, and #4
correspond to #6 and #7 respectively from the original series.

For the content of these patches then:

  #1, #2 - These are pretty simple testsuite changes.

  #3, #4 - I've updated these after the feedback from Eli and Tom in
   the original series, but the docs especially probably need another
   review.  The general strategy is mostly unchanged, but I now cover
   additional cases to handle .debug_names and .gdb_index.

Thanks,
Andrew

--

Andrew Burgess (4):
  gdb/testsuite: Allow cc-with-tweaks board file to be used with Fortran
  gdb/fortran: Add test for module variables in 'info variables' output
  gdb/fortran: Add new 'info modules' command
  gdb: Add new commands to list module variables and functions

 gdb/ChangeLog                              |  31 +++
 gdb/NEWS                                   |  18 ++
 gdb/doc/ChangeLog                          |   9 +
 gdb/doc/gdb.texinfo                        |  32 +++
 gdb/dwarf2read.c                           |  25 +++
 gdb/psymtab.c                              |   2 +
 gdb/symtab.c                               | 347 ++++++++++++++++++++++++++++-
 gdb/symtab.h                               |   5 +-
 gdb/testsuite/ChangeLog                    |  24 ++
 gdb/testsuite/boards/cc-with-tweaks.exp    |  10 +
 gdb/testsuite/gdb.fortran/info-modules.exp | 181 +++++++++++++++
 gdb/testsuite/gdb.fortran/info-types.exp   |   6 +-
 gdb/testsuite/gdb.fortran/info-types.f90   |  36 +++
 gdb/testsuite/gdb.fortran/module.exp       |  24 ++
 14 files changed, 743 insertions(+), 7 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/info-modules.exp

-- 
2.14.5


             reply	other threads:[~2019-10-03 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 11:29 Andrew Burgess [this message]
2019-10-03 11:29 ` [PATCHv2 3/4] gdb/fortran: Add new 'info modules' command Andrew Burgess
2019-10-03 16:12   ` Eli Zaretskii
2019-10-03 11:29 ` [PATCHv2 1/4] gdb/testsuite: Allow cc-with-tweaks board file to be used with Fortran Andrew Burgess
2019-10-03 11:29 ` [PATCHv2 4/4] gdb: Add new commands to list module variables and functions Andrew Burgess
2019-10-03 16:16   ` Eli Zaretskii
2019-10-10 15:58   ` Tom Tromey
2019-11-22 12:44   ` Tom de Vries
2019-11-27 21:29     ` Andrew Burgess
2019-11-28  9:21       ` Tom de Vries
2019-11-28 12:18         ` Andrew Burgess
2019-10-03 11:29 ` [PATCHv2 2/4] gdb/fortran: Add test for module variables in 'info variables' output Andrew Burgess
2019-10-10 15:59 ` [PATCHv2 0/4] Fortran info types, info modules, info module Tom Tromey

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.1570101531.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@embecosm.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