From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] decimal float point patch based on libdecnumber: testcase
Date: Fri, 23 Jun 2006 19:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0606240320180.2746@localhost.localdomain> (raw)
In-Reply-To: <20060623184946.GA32680@nevyn.them.org>
So what is XFAIL intended for? In my opinion, it is intended for failure,
but an expected failure. I guess it can be used for such situation like:
the output is expected, but is not what we want at last. We might fix
that at a later time.
Just my two cents anyway. Correct me if I am wrong.
Thanks
- Wu Zhou
On Fri, 23 Jun 2006, Daniel Jacobowitz wrote:
> On Sat, Jun 24, 2006 at 02:39:41AM +0800, Wu Zhou wrote:
> > > > Do you mean that we need to output something more close to the fact. to
> > > > say, "Addition/Multiple of decimal floating point is not supported right
> > > > now". or something other like this. If you want, I can do that.
> > >
> > > No, I think what's there is fine - but add a test or two for that error
> > > message.
> >
> > OK. Understand. We can use XFAIL for them, right?
>
> I mean tests that PASS given the current state - for now, it's what we
> want to happen, so test that it does happen.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
next prev parent reply other threads:[~2006-06-23 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 21:03 Wu Zhou
2006-06-21 23:36 ` [RFC] decimal float point patch based on libdecnumber: gdb patch Wu Zhou
2006-06-22 3:27 ` Eli Zaretskii
2006-06-22 14:18 ` Wu Zhou
2006-07-12 20:39 ` Daniel Jacobowitz
2006-06-22 20:25 ` [RFC] decimal float point patch based on libdecnumber: testcase Daniel Jacobowitz
2006-06-22 23:27 ` Wu Zhou
2006-06-23 2:38 ` Daniel Jacobowitz
2006-06-23 18:39 ` Wu Zhou
2006-06-23 18:49 ` Daniel Jacobowitz
2006-06-23 19:25 ` Wu Zhou [this message]
2006-06-23 19:51 ` Daniel Jacobowitz
2006-07-11 15:35 Wu Zhou
2006-07-12 17:16 ` 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=Pine.LNX.4.64.0606240320180.2746@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=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