From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: qiyaoltc@gmail.com
Subject: [PATCH v3 0/6] Some Fortran Patches
Date: Fri, 11 Aug 2017 11:07:00 -0000 [thread overview]
Message-ID: <1502449611-8865-1-git-send-email-tim.wiederhake@intel.com> (raw)
Hi all,
this is a set of mostly unrelated Fortran patches that were originally written
by Bernhard Heckel.
V1 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-07/msg00317.html
V2 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-07/msg00317.html
Changes since V2:
* Removed unneccesary variable in f_type_print_varspec_suffix.
* Unified "runto MAIN__" in tests.
* Replaced kfail with xfail in tests.
* Patch #6 mentions changes in the correct ChangeLog.
Patch #1 was OK'd by Yao.
Patch #6 (documentation) was OK'd by Eli.
I believe I have addressed all feedback I got so far, please let me know If I
missed something.
Regards,
Tim
*** BLURB HERE ***
Bernhard Heckel (6):
DWARF: Don't add nameless modules to partial symbol table.
Fortran: Accessing fields of inherited types via fully qualified name.
Fortran: Ptype, print type extension.
Dwarf: Fortran, support DW_TAG_entry_point.
Fortran: Enable setting breakpoint on nested functions.
Fortran: Nested functions, add scope parameter.
gdb/doc/gdb.texinfo | 3 +
gdb/dwarf2read.c | 144 +++++++++++++++++++++++---
gdb/f-exp.y | 7 +-
gdb/f-typeprint.c | 28 ++++-
gdb/testsuite/gdb.fortran/block-data.exp | 49 +++++++++
gdb/testsuite/gdb.fortran/block-data.f | 56 ++++++++++
gdb/testsuite/gdb.fortran/entry_point.exp | 70 +++++++++++++
gdb/testsuite/gdb.fortran/entry_point.f90 | 48 +++++++++
gdb/testsuite/gdb.fortran/nested-funcs.exp | 28 +++++
gdb/testsuite/gdb.fortran/nested-funcs.f90 | 66 +++++++++++-
gdb/testsuite/gdb.fortran/oop_extend_type.exp | 113 ++++++++++++++++++++
gdb/testsuite/gdb.fortran/oop_extend_type.f90 | 56 ++++++++++
gdb/valops.c | 6 ++
13 files changed, 654 insertions(+), 20 deletions(-)
create mode 100644 gdb/testsuite/gdb.fortran/block-data.exp
create mode 100644 gdb/testsuite/gdb.fortran/block-data.f
create mode 100644 gdb/testsuite/gdb.fortran/entry_point.exp
create mode 100644 gdb/testsuite/gdb.fortran/entry_point.f90
mode change 100755 => 100644 gdb/testsuite/gdb.fortran/nested-funcs.exp
mode change 100755 => 100644 gdb/testsuite/gdb.fortran/nested-funcs.f90
create mode 100644 gdb/testsuite/gdb.fortran/oop_extend_type.exp
create mode 100644 gdb/testsuite/gdb.fortran/oop_extend_type.f90
--
2.7.4
next reply other threads:[~2017-08-11 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:07 Tim Wiederhake [this message]
2017-08-11 11:07 ` [PATCH v3 3/6] Fortran: Ptype, print type extension Tim Wiederhake
2017-08-23 11:05 ` Yao Qi
2017-08-24 12:36 ` Wiederhake, Tim
2017-08-11 11:07 ` [PATCH v3 6/6] Fortran: Nested functions, add scope parameter Tim Wiederhake
2017-09-04 9:58 ` Yao Qi
2017-09-08 12:13 ` Wiederhake, Tim
2017-08-11 11:07 ` [PATCH v3 4/6] Dwarf: Fortran, support DW_TAG_entry_point Tim Wiederhake
2017-09-04 8:37 ` Yao Qi
2017-08-11 11:07 ` [PATCH v3 2/6] Fortran: Accessing fields of inherited types via fully qualified name Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 1/6] DWARF: Don't add nameless modules to partial symbol table Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 5/6] Fortran: Enable setting breakpoint on nested functions Tim Wiederhake
2017-09-04 9:22 ` Yao Qi
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=1502449611-8865-1-git-send-email-tim.wiederhake@intel.com \
--to=tim.wiederhake@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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