Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Document patch for F90 derived type support
Date: Thu, 02 Mar 2006 02:43:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0603012136550.18903@localhost.localdomain> (raw)
In-Reply-To: <uek1m3gzo.fsf@gnu.org>


On Wed, 1 Mar 2006, Eli Zaretskii wrote:

> > Date: Tue, 28 Feb 2006 21:51:24 -0500 (EST)
> > From: Wu Zhou <woodzltc@cn.ibm.com>
> > cc: gdb-patches@sources.redhat.com
> > 
> > I did some comparison between g77 and gfortran.  In the aspect of the 
> > compiler-generated DW_TAG_base_type, g77 uses "byte", "word" and "integer" 
> > for "integer*1", "integer*2" and "integer*4" respectively.  And gfortran 
> > seems to adopt a new mechanism, it uses "int1", "int2" and "int4" 
> > respectively.  So it might also make some sense.  At lease the debugger 
> > user can guess the meaning from these words.  :-) 
> 
> So you now think that it is not a good idea to display "integer*4"
> instead of "int4"?  I thought you previously agreed with me that the
> former was better, from the user point of view.

Eli, I am still with you.  The former is surely better for the user.  
But I am not sure yet which should be fixed, the compiler or the 
debugger.

I proposed another method, which depends on TYPE_CODE (type) and 
TYPE_LENGTH (type) to determine what to be displayed at last. How do you 
think on that?  (I sent out that proposal a while ago)

> GDB is a debugger.  If it were a program to display DWARF-2 debug
> info, then it should have displayed exactly what is written in there.
> But as a debugger, it should display something that is sensible to the
> user of a debugger, i.e. it needs to speak the programming language of
> the source, not DWARF.

Good stand.  I agree with you on this too.  :-)

Regards
- Wu Zhou


  reply	other threads:[~2006-03-02  2:43 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
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 [this message]
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=Pine.LNX.4.64.0603012136550.18903@localhost.localdomain \
    --to=woodzltc@cn.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.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