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] Decimal Floating Point support for GDB (Part 1: patch)
Date: Thu, 29 Sep 2005 05:14:00 -0000	[thread overview]
Message-ID: <1127970854.433b782619db1@imap.linux.ibm.com> (raw)

Hi Eli,

Thanks for your reply.

Quoting Eli Zaretskii <eliz@gnu.org>:

> I'm not sure; the similar "1234.565f" feature is not documented
> anywhere.  I guess the idea is that a programmer in the C language
> should know about this C feature, and GDB just supports the C language
> by accepting its syntax for numbers.  Isn't the same true for your
> additions, i.e., isn't "1234.56df" going to be a valid C number
> syntax?

Yes.  "1234.56df" will be valid number in incoming c99 revison.  This is 
documented in http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1107.htm

> > What about gdb internal?  Do we need to update that too?
> 
> gdbint.texinfo should have a description of language-specific files,
> what they do and how to build one for a new language.  One minor issue
> that should be part of that description is the number syntax.  I'd be
> thrilled to see such a description added to gdbint, but since there's
> no such description now, I don't feel I can ask you to write a tiny
> addition to a non-existent chapter.  But if you can find time to write
> a full description of the C expression syntax support, I'd gratefully
> review it.

OK.  Got it.  I will try to see whether I can find any time to work on 
that.  But I am not sure.  So I can't promise anything at this time.  :-)

> > 2. As you might know, dfp for gcc is also under development. And my patch 
> > depends on the availablity of that?  How did gdb handle this kind of 
> > situation before?  Did we need to wait until dfp is ready for gcc?
> 
> There's no need to wait, IMHO, since this feature in GDB will not
> cause any harm unless and until GDB sees some program whose DWARF info
> includes these special tags.

That is good.  I wish it is like this too.

Regards
- Wu Zhou


             reply	other threads:[~2005-09-29  5:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  5:14 Wu Zhou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-28  4:40 Wu Zhou
2005-09-28 18:40 ` Eli Zaretskii
2005-09-29  2:12   ` Wu Zhou
2005-09-29  3:34     ` Eli Zaretskii
2005-10-02 21:00 ` Daniel Jacobowitz
2005-10-09  5:23   ` Wu Zhou
2005-10-09 20:08     ` Daniel Jacobowitz
2005-10-12 14:42       ` Wu Zhou
2005-10-12 14:49         ` Daniel Jacobowitz

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=1127970854.433b782619db1@imap.linux.ibm.com \
    --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