From: Eli Zaretskii <eliz@gnu.org>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, qiyaoltc@gmail.com,
bernhard.heckel@intel.com
Subject: Re: [PATCH v4 4/5] Dwarf: Fortran, support DW_TAG_entry_point.
Date: Fri, 08 Sep 2017 14:35:00 -0000 [thread overview]
Message-ID: <83efrhxnr3.fsf@gnu.org> (raw)
In-Reply-To: <1504877571-22441-5-git-send-email-tim.wiederhake@intel.com> (message from Tim Wiederhake on Fri, 8 Sep 2017 15:32:50 +0200)
> From: Tim Wiederhake <tim.wiederhake@intel.com>
> Cc: qiyaoltc@gmail.com, Bernhard Heckel <bernhard.heckel@intel.com>
> Date: Fri, 8 Sep 2017 15:32:50 +0200
>
> gdb/ChangeLog:
> PR fortran/8043
> PR fortran/9279
> * NEWS: Mention DW_TAG_entry_point support.
> * gdb/dwarf2read.c (add_partial_symbol): Handle DW_TAG_entry_point.
> (add_partial_entry_point): New function.
> (add_partial_subprogram): Search for entry_points.
> (process_die): Handle DW_TAG_entry_point.
> (dwarf2_get_pc_bounds): Update low pc from DWARF.
> (load_partial_dies): Save DW_TAG_entry_point's.
> (load_partial_dies): Save DW_TAG_entry_point to hash table.
> (load_partial_dies): Look into child's of DW_TAG_sub_program
> for fortran.
> (new_symbol_full): Process DW_TAG_entry_point.
> (read_type_die_1): Handle DW_TAG_entry_point.
>
> gdb/testsuite/ChangeLog:
> * gdb.fortran/entry_point.f90: New file.
> * gdb.fortran/entry_point.exp: New file.
OK for the change in NEWS.
Thanks.
next prev parent reply other threads:[~2017-09-08 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:33 [PATCH v4 0/5] Some Fortran Patches Tim Wiederhake
2017-09-08 13:33 ` [PATCH v4 1/5] DWARF: Don't add nameless modules to partial symbol table Tim Wiederhake
2017-09-08 13:33 ` [PATCH v4 4/5] Dwarf: Fortran, support DW_TAG_entry_point Tim Wiederhake
2017-09-08 14:35 ` Eli Zaretskii [this message]
2017-09-08 13:33 ` [PATCH v4 5/5] Fortran: Nested functions, add scope parameter Tim Wiederhake
2017-09-08 14:34 ` Eli Zaretskii
2017-09-08 13:33 ` [PATCH v4 3/5] Fortran: Ptype, print type extension Tim Wiederhake
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=83efrhxnr3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tim.wiederhake@intel.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