From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [RFC]: Document patch for F90 derived type support
Date: Fri, 03 Mar 2006 09:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0603022020550.9815@localhost.localdomain> (raw)
In-Reply-To: <20060302044018.GA26360@nevyn.them.org>
On Wed, 1 Mar 2006, Daniel Jacobowitz wrote:
> On Thu, Mar 02, 2006 at 06:36:03AM +0200, Eli Zaretskii wrote:
> > > Date: Wed, 1 Mar 2006 21:33:35 -0500 (EST)
> > > From: Wu Zhou <woodzltc@cn.ibm.com>
> > > cc: gdb-patches@sourceware.org
> > >
> > > Maybe we can do this:
> > >
> > > case TYPE_CODE_INT:
> > > /* There may be some character types that attempt to come
> > > through as TYPE_CODE_INT since dbxstclass.h is so
> > > C-oriented, we must change these to "character" from "char". */
> > >
> > > if (strcmp (TYPE_NAME (type), "char") == 0)
> > > fprintfi_filtered (level, stream, "character");
> > > else
> > > fprintfi_filtered (level, stream, "integer (%d)", TYPE_LENGTH (type));
> > > break;
> > >
> > > The basic idea is to let the TYPE_CODE (type) and TYPE_LENGTH (type) to
> > > determine what should be displayed.
> >
> > This is okay with me. Thanks.
>
> Me too, I suppose. If you're going to go this route, take a look at
> the full set of types that gfortran prints out useless names for,
> please. It's in gcc/fortran/trans-type.c.
OK. I will. If I have time, I will see if I can also make a patch
for gfortran. Thanks for the pointer.
Regards
- Wu Zhou
next prev parent reply other threads:[~2006-03-03 1:21 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 [this message]
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=Pine.LNX.4.64.0603022020550.9815@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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