public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch master updated. 530e8392d7d5d4a831c5ce0e4cd410e1c4bd166a
Date: Thu, 19 Dec 2013 12:18:00 -0000	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  530e8392d7d5d4a831c5ce0e4cd410e1c4bd166a (commit)
       via  7f9b20bb352768e14cfa7361a82373b8539bebed (commit)
      from  f6ec89e7bc631c0bd48cb6c4b960b29266e19550 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------;h=530e8392d7d5d4a831c5ce0e4cd410e1c4bd166a

commit 530e8392d7d5d4a831c5ce0e4cd410e1c4bd166a
Author: Keven Boell <>
Date:   Fri Nov 15 11:32:01 2013 +0100

    fortran: enable ptype/whatis for modules.
    Added new domain MODULE_DOMAIN for fortran modules to avoid
    issues with sharing namespaces (e.g. when a variable currently
    in scope has the same name as a module).
    	(gdb) ptype modname
    	old> No symbol "modname" in current context.
    	new> type = module modname
    This fixes PR 15209 and also addresses the issue
    with sharing namespaces:
    2013-11-19  Keven Boell  <>
                Sanimir Agovic  <>
    	* cp-namespace.c (cp_lookup_nested_symbol): Enable
    	nested lookups for fortran modules.
    	* dwarf2read.c (read_module): Add fortran module to
    	the symbol table.
    	(add_partial_symbol, add_partial_module): Add fortran
    	module to the partial symbol table.
    	(new_symbol_full): Create full symbol for fortran module.
    	* f-exp.y (yylex): Add new module domain to be parsed.
    	* symtab.h: New domain for fortran modules.
    	* gdb.fortran/module.exp: Completion matches fortran module
    	names as well. ptype/whatis on modules return a proper type.
    	Add new check for having the correct scope.;h=7f9b20bb352768e14cfa7361a82373b8539bebed

commit 7f9b20bb352768e14cfa7361a82373b8539bebed
Author: Keven Boell <>
Date:   Fri Oct 25 12:10:57 2013 +0100

    fortran: enable ptype/whatis for user defined types.
    	(gdb) ptype type
    	old> No symbol "type" in current context.
    	new> type = Type type
    	     integer(kind=4) :: t_i
    	     End Type type
    2013-11-19  Sanimir Agovic  <>
                Keven Boell  <>
    	* f-exp.y (yylex): Add domain array to enable lookup
    	in multiple domains. Loop over lookup domains and try
    	to find requested symbol. Add STRUCT_DOMAIN to lookup
    	domains to be able to query for user defined types.
    	* gdb.fortran/type.f90: New file.
    	* gdb.fortran/whatis_type.f90: New file.


Summary of changes:
 ChangeLog                                 |   19 +++++++++++
 gdb/cp-namespace.c                        |    4 ++
 gdb/dwarf2read.c                          |   20 ++++++++++++
 gdb/f-exp.y                               |   38 +++++++++++++++-------
 gdb/symtab.h                              |    4 ++
 gdb/testsuite/ChangeLog                   |   11 ++++++
 gdb/testsuite/gdb.fortran/module.exp      |   13 ++++++--
 gdb/testsuite/gdb.fortran/module.f90      |   12 +++++++
 gdb/testsuite/gdb.fortran/type.f90        |   28 +++++++++++++++++
 gdb/testsuite/gdb.fortran/whatis_type.exp |   48 +++++++++++++++++++++++++++++
 10 files changed, 182 insertions(+), 15 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/type.f90
 create mode 100644 gdb/testsuite/gdb.fortran/whatis_type.exp

gdb and binutils

                 reply	other threads:[~2013-12-19 12:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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