public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gladman <brg@gladman.plus.com>
To: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: GSL test release 1.12.90
Date: Fri, 14 Aug 2009 11:50:00 -0000	[thread overview]
Message-ID: <4A854F64.9050006@gladman.plus.com> (raw)

I have compiled GSL 1.12.90 and the tests on Vista x64 Ultimate using
Visual Studio 2008 Professional (a few minor changes are needed to do
this).

I had two compile errors:

1. I found declarations after executable statements in test_funcs.c
(spring_f)

2. In gsl_const_cgs.h, the MSVC preprocessor does not recognise the
#warning directive.

After removing these compilation errors, all tests except one pass in
both 32 and 64 bit versions of the library.

The test that fails is testrandist, which gives this output in 64-bit mode:

GSL_IEEE_MODE="double-precision,round-to-nearest,mask-all"
FAIL: test gsl_ran_exponential [0,1]
      (0 observed vs 0.393469 expected) [7]

and this in 32-bit mode:

GSL_IEEE_MODE="double-precision,round-to-nearest,mask-all"
FAIL: test gsl_ran_exponential [0,1]
      (0 observed vs 0.393469 expected) [7]
FAIL: test gsl_ran_discrete1 [-0.5,0.5]
      (0.33122 observed vs 0.59 expected) [9]
FAIL: test gsl_ran_discrete1 [0.5,1.5]
      (0.33343 observed vs 0.4 expected) [10]
FAIL: test gsl_ran_discrete1 [1.5,3.5]
      (0.33164 observed vs 0.01 expected) [11]

I have not yet had time to look into this failure any further.

My thanks to all developers for their first class work on GSL.

  Brian Gladman



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4334 (20090814) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


             reply	other threads:[~2009-08-14 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 11:50 Brian Gladman [this message]
2009-08-17 10:08 ` Brian Gough
2009-08-18 11:04   ` Brian Gladman
2009-09-09 22:47   ` GNU Scientific Library 1.13 released - report maxgacode

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=4A854F64.9050006@gladman.plus.com \
    --to=brg@gladman.plus.com \
    --cc=gsl-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).