From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18555 invoked by alias); 28 Feb 2006 13:53:28 -0000 Received: (qmail 18534 invoked by uid 22791); 28 Feb 2006 13:53:27 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 28 Feb 2006 13:53:16 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FE5Hq-0006ds-Vc; Tue, 28 Feb 2006 08:53:11 -0500 Date: Tue, 28 Feb 2006 15:05:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Wu Zhou , gdb-patches@sources.redhat.com Subject: Re: [RFC]: Document patch for F90 derived type support Message-ID: <20060228135310.GA25487@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Wu Zhou , gdb-patches@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00506.txt.bz2 On Tue, Feb 28, 2006 at 07:37:46AM +0200, Eli Zaretskii wrote: > > Date: Sun, 26 Feb 2006 23:34:40 -0500 (EST) > > From: Wu Zhou > > cc: gdb-patches@sources.redhat.com > > > > > > + type = Type bar > > > > + int4 :: c > > > > + real*4 :: d > > > > + End Type bar > > > > > > Btw, isn't it more consistent to print "integer*4" instead of "int4"? > > > Either that, or just "integer", I think. Or is "int4" a valid type > > > name in f90? (The last Fortran I used was f77, so please forgive my > > > ignorance.) > > > > Yes. I also think so. But the name of "int4" is got from the DWARF tag: > > > > <1>: Abbrev Number: 4 (DW_TAG_base_type) > > DW_AT_name : int4 > > DW_AT_byte_size : 4 > > DW_AT_encoding : 5 (signed) > > Well, we don't need t print everything DWARF-2 throws at us verbatim. > If you agree with my suggestions, I say let's use them. Are there any > problems with that? Normally we try to honor the type names in debug info. If int4 is a bogus name for a type in Fortran, then this debug info is bogus - gfortran should be fixed. -- Daniel Jacobowitz CodeSourcery