From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6916 invoked by alias); 28 Jun 2011 16:58:12 -0000 Received: (qmail 6895 invoked by uid 22791); 28 Jun 2011 16:58:10 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mx02.qsc.de (HELO mx02.qsc.de) (213.148.130.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jun 2011 16:57:54 +0000 Received: from [192.168.178.22] (port-92-204-88-186.dynamic.qsc.de [92.204.88.186]) by mx02.qsc.de (Postfix) with ESMTP id DA1E41DB11; Tue, 28 Jun 2011 18:57:47 +0200 (CEST) Message-ID: <4E0A0809.6040104@net-b.de> Date: Tue, 28 Jun 2011 16:58:00 -0000 From: Tobias Burnus User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110414 SUSE/3.1.10 Thunderbird/3.1.10 MIME-Version: 1.0 To: Michael Eager CC: gcc@gcc.gnu.org, fortran@gcc.gnu.org Subject: Re: RFC: DWARF debug tags for gfortran's OOP implementation References: <4E08C03C.1040706@net-b.de> <4E09E34C.8050405@eagerm.com> In-Reply-To: <4E09E34C.8050405@eagerm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg00365.txt.bz2 On 06/28/2011 04:21 PM, Michael Eager wrote: > DWARF has attributes for accessibility (e.g., public, private). If the > attributes are similar to those for C++, you should generate them in a > similar fashion. Well, Fortran has public and private - but I am not sure in how far it matches C++'s public and private (cf. also below). > I'm not sure what "type extension" means. Type extension is inheritance, i.e. Fortran's type parent end type parent type, extends(parent) :: child end type child matches C++'s class parent {}; class child : public parent { }; > If there is > a comparable feature in C++ or other languages supported by DWARF, you > should generate similar DWARF info. I think that's to a certain extend my problem: I do not completely understand the current DWARF - nor the fine points of C++ to see in how far it matches. For instance: While both in C++ and Fortran variables and methods can be public or private, Fortran just extends a type without having a concept of public/private/protected inheritance. The semantics of Fortran's public, private and protected is related to modules - which does not really match C++ concept. The DWARF spec does not really tell the implications of the accessibility tags, which makes it a tad more difficult to understand what should be done. I think we will start by marking the VTABLE as such and to try to handle member functions. - And do compare how g++/gdb handle the approximate C++ version. Tobias