public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49475] New: [OOP] Add DWARF info for Fortran's OOP features (extension, member functions)
Date: Mon, 20 Jun 2011 16:30:00 -0000	[thread overview]
Message-ID: <bug-49475-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49475

           Summary: [OOP] Add DWARF info for Fortran's OOP features
                    (extension, member functions)
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


We should consider generating DWARF information for Fortran OOP features:

type t
  integer :: a
end type t

type, EXTENDS(t) :: t2
  integer :: b
contains
  procedure :: member_proc => local_proc
end type t2

type (t2) :: x


In this example, x%a and x%t2%a access the component of the parent type.

"member_proc" is a member function, which can be accessed as x%member_proc();
the actual function being called depends on the dynamic type and is determined
via the vtable.


DWARF4 does not really state what should be used in case of Fortran. At
http://www.dwarfstd.org/doc/DWARF4.pdf one finds:
- "5.5.3 Derived or Extended Structs, Classes and Interfaces"
- "5.5.7 Member Function Entries"


             reply	other threads:[~2011-06-20 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 16:30 burnus at gcc dot gnu.org [this message]
2011-07-07 13:34 ` [Bug fortran/49475] [OOP][debugging] " burnus at gcc dot gnu.org
2015-10-29 13:46 ` dominiq at lps dot ens.fr
2023-03-07 14:20 ` tromey at gcc dot gnu.org

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=bug-49475-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).