From: Janus Weil <janus@gcc.gnu.org>
To: Tobias Burnus <burnus@net-b.de>
Cc: GCC Mailing List <gcc@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: RFC: DWARF debug tags for gfortran's OOP implementation
Date: Tue, 28 Jun 2011 12:13:00 -0000 [thread overview]
Message-ID: <BANLkTinHsVJri-he5TfRR+7eBv9QiSOMEA@mail.gmail.com> (raw)
In-Reply-To: <4E08C03C.1040706@net-b.de>
Hi Tobias,
> during the GCC Gathering I realized during the LTO debugging symbol
> discussion that gfortran does not generate debug information for the OOP
> features (cf. PR 49475).
Btw, how was the London meeting? Anything interesting to report (Fortran-wise)?
> The first issue to solve is which DWARF information one should generate. I
> have only very limited knowledge of DWARF, except that I quickly scanned
> "5.5.3 Derived or Extended Structs, Classes and Interfaces" and "5.5.7
> Member Function Entries" (of http://www.dwarfstd.org/doc/DWARF4.pdf).
>
> I think one should handle member functions (cf. example below). I am not
> sure whether other things like type extension or accessibility should be
> handled.
Well, in principle all of those should be handled, I guess.
I don't have any experience with DWARF either, but maybe I'll look
into it, once I have gotten some of the more nasty OOP
bugs/regressions out of the way.
How would one tackle this practically? All the DWARF stuff is
generated in the middle-end, I assume (and probably the type
extension/member function info is already there for C++, right?). So,
the question is: What do we need to do in the front end, in order to
make the middle-end emit the right DWARF info?
Cheers,
Janus
next prev parent reply other threads:[~2011-06-28 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 17:39 Tobias Burnus
2011-06-28 12:13 ` Janus Weil [this message]
2011-06-28 13:19 ` Tobias Burnus
2011-06-28 14:21 ` Michael Eager
2011-06-28 15:45 ` Janus Weil
2011-06-28 16:58 ` Tobias Burnus
2011-06-28 18:37 ` Tom Tromey
2011-06-28 19:19 ` Michael Eager
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=BANLkTinHsVJri-he5TfRR+7eBv9QiSOMEA@mail.gmail.com \
--to=janus@gcc.gnu.org \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).