public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Dalibor Topic <robilad@yahoo.com>
Cc: Anthony Green <green@redhat.com>, mauve-discuss@sources.redhat.com
Subject: Re: 600+ BigDecimal tests
Date: Sat, 18 Jan 2003 16:05:00 -0000	[thread overview]
Message-ID: <1042905877.24536.344.camel@elsschot> (raw)
In-Reply-To: <20030118152741.13418.qmail@web10002.mail.yahoo.com>

Hi,

On Sat, 2003-01-18 at 16:27, Dalibor Topic wrote:
> Aah, that's a "known defect" ;) You need to install
> the gnu mp libs for arbitrary precision mathematics
> first ( http://www.swox.com/gmp/ ), and then recompile
> kaffe to pick it up.

Thanks. I just used the kaffe 1.0.7 Debian package which has the correct
dependencies. Results:

FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: has001 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov013 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov014 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov015 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov016 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov017 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov019 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov105 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov106 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov107 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov109 (number 1)
14 of 285 tests failed

I have now also tried the Blackdown-1.4.1-beta which gives:

FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div376 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div203 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div204 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mul038 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: has001 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: has002 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov107 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: sca007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc100 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val100 (number 1)
11 of 600 tests failed

And here are the Classpath ones again just for comparison:

FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div377 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div203 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: div204 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mul038 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: has001 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: lov107 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpl007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: mpr007 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc005 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc006 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc100 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc101 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: ssc102 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val008 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val013 (number 1)
FAIL: gnu.testlet.java.math.BigDecimal.DiagBigDecimal: val100 (number 1)
21 of 338 tests failed

Hmmm. This will be fun figuring out what goes wrong where and wether it
is the testcase or the implementation that is incorrect (has001, lov007
and lov107 at least look suspicious since all three implementations get
those wrong).

Note that you will need my patch to get these results, without it both
the gcj and kaffe version give up almost immediatly with a
NumberFormatException that is never caught.

Cheers,

Mark

  reply	other threads:[~2003-01-18 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22 14:58 Anthony Green
2003-01-03  1:35 ` Mark Wielaard
2003-01-17 19:26   ` Mark Wielaard
2003-01-18 15:27     ` Dalibor Topic
2003-01-18 16:05       ` Mark Wielaard [this message]
2003-01-19 23:40         ` Stephen Crawley
2003-01-20  0:09           ` Anthony Green
2003-01-20  0:25             ` Stephen Crawley
2003-01-20  1:21               ` Artur Biesiadowski
2003-01-20  2:11                 ` Stephen Crawley
2003-01-20  9:48             ` Dalibor Topic
2003-01-20  0:06   ` Anthony Green

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=1042905877.24536.344.camel@elsschot \
    --to=mark@klomp.org \
    --cc=green@redhat.com \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=robilad@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).