Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Document patch for F90 derived type support
Date: Tue, 28 Feb 2006 15:05:00 -0000	[thread overview]
Message-ID: <20060228135310.GA25487@nevyn.them.org> (raw)
In-Reply-To: <u64n0qc0l.fsf@gnu.org>

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 <woodzltc@cn.ibm.com>
> > 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><e6>: 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


  reply	other threads:[~2006-02-28 13:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24  8:13 Wu Zhou
2006-02-24  8:34 ` Eli Zaretskii
2006-02-27  5:59   ` Wu Zhou
2006-02-28  6:43     ` Eli Zaretskii
2006-02-28 15:05       ` Daniel Jacobowitz [this message]
2006-02-28 20:09         ` Eli Zaretskii
2006-03-01  2:51           ` Wu Zhou
2006-03-01  4:32             ` Daniel Jacobowitz
2006-03-01  4:53               ` Eli Zaretskii
2006-03-01  5:05                 ` Daniel Jacobowitz
2006-03-01 19:02                   ` Eli Zaretskii
2006-03-01 19:38                     ` Daniel Jacobowitz
2006-03-02  2:32                       ` Wu Zhou
2006-03-02  4:36                         ` Eli Zaretskii
2006-03-02  4:40                           ` Daniel Jacobowitz
2006-03-03  9:09                             ` Wu Zhou
2006-03-02  4:25                       ` Eli Zaretskii
2006-03-02  4:27                         ` Daniel Jacobowitz
2006-03-01  4:51             ` Eli Zaretskii
2006-03-02  2:43               ` Wu Zhou
2006-03-02  3:22                 ` Daniel Jacobowitz
2006-03-02  4:38                   ` Eli Zaretskii
2006-03-02  4:37                 ` Eli Zaretskii

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=20060228135310.GA25487@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.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