From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC]: Document patch for F90 derived type support
Date: Thu, 02 Mar 2006 04:27:00 -0000 [thread overview]
Message-ID: <20060302042721.GA26005@nevyn.them.org> (raw)
In-Reply-To: <uy7zt3223.fsf@gnu.org>
On Thu, Mar 02, 2006 at 06:25:56AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 1 Mar 2006 14:38:29 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > > Perhaps I'm confused: isn't "int4" a 32-bit integer? I thought it
> > > was, but if I was mistaken, my apologies for the noise.
> >
> > It's not reserved at all in the input to the compiler - it might be
> > something different than a type, or it might be the name of a record
> > type (whatever the correct name for that is).
>
> I'm still not sure I understand, but I think you do agree that this is
> a 32-bit integer. In that case, I maintain that we should display
> "integer(4)", not "int4".
Sorry, I am not expressing myself well.
The fact that it is named "int4" in debug output doesn't mean that it
is a 32-bit integer. The fact that it is a 32-bit integer, in turn,
may mean that we could choose to ignore its name if that was
worthwhile.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-02 4:27 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 [this message]
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=20060302042721.GA26005@nevyn.them.org \
--to=drow@false.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