From: Eli Zaretskii <eliz@gnu.org>
To: 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 20:09:00 -0000 [thread overview]
Message-ID: <u1wxnqmnf.fsf@gnu.org> (raw)
In-Reply-To: <20060228135310.GA25487@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 28 Feb 2006 08:53:10 -0500)
> Date: Tue, 28 Feb 2006 08:53:10 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sources.redhat.com
>
> Normally we try to honor the type names in debug info.
If they make sense, sure. If they don't, I don't think we should
blindly follow them.
> If int4 is a bogus name for a type in Fortran, then this debug info
> is bogus - gfortran should be fixed.
I agree, but at least one version of gfortran that uses int4 is
already out there, so I suggest that GDB handles that as we think it's
right.
next prev parent reply other threads:[~2006-02-28 20:00 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 [this message]
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=u1wxnqmnf.fsf@gnu.org \
--to=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