From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Decimal Floating Point support for GDB (Part 2: testcase)
Date: Sun, 02 Oct 2005 21:05:00 -0000 [thread overview]
Message-ID: <20051002210053.GA32664@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0509281256030.1231@linux.site>
On Wed, Sep 28, 2005 at 01:28:07PM +0800, Wu Zhou wrote:
> In this testcase, there are totally 83 tests. Most of them are about
> displaying and setting of dfp types, which are partitioned into
> three groups, one for each dfp types (_Decimal32, _Decimal64 and
> _Decimal128). In each group, we first begin with the printing of
> a normal finite dfp value, then Infinity and NaN. Then we call
> d32_set_tests (d64_set_tests or d128_set_tests) to test that GDB
> could handle the setting different values of variable d32 (d64 or
> d128).
>
> At the end of the testcase, we test that GDB could print out the dfp
> values correctly in the function arguments and backtrace.
Just a few comments on the tests:
- This should be at least two separate tests, since the "p 1.5df" tests
can be run without a GCC which supports DFP, even though dfp-test.c
can't be compiled.
- C files need to have copyright headers.
In this:
> + gdb_test "p d32=123.45df" "123.45df" "p d32=123.45df"
- The third argument to gdb_test defaults to the first argument, so you
don't need it.
- The second argument should be more specific. Something like
"\$${decimal} = 123.45df". I went to look at this test to see if my
understanding of the use of string types was right, and the matching
patterns were so loose I couldn't tell.
Otherwise I'll wait to look at this further until we're agreed on the
GDB support.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-02 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 5:26 Wu Zhou
2005-10-02 21:05 ` Daniel Jacobowitz [this message]
2005-10-18 10:17 ` [RFC] Decimal Floating Point support for GDB (Part 2: testcase - Revised) Wu Zhou
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=20051002210053.GA32664@nevyn.them.org \
--to=drow@false.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