unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Rob Browning" <rlb@defaultvalue.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Just in case...
Date: Tue, 12 Aug 2008 21:36:33 +0100	[thread overview]
Message-ID: <49dd78620808121336l6604a5e1m9d0e531c24b5580b@mail.gmail.com> (raw)
In-Reply-To: <49dd78620808120737t68d167e4ob2768e88804da22c@mail.gmail.com>

2008/8/12 Neil Jerram <neiljerram@googlemail.com>:
>
> I'll try to take a look at the m68k prob tonight.

No solution yet I'm afraid, so any thoughts would be appreciated.

It seems to be a fairly obscure rounding test that is failing:

      x = ldexp (1.0, DBL_MANT_DIG - 1) - 1.0 + 0.5;
      want = ldexp (1.0, DBL_MANT_DIG - 1);
      assert (scm_c_round (x) == want);

i.e., IIUC, testing rounding near the upper limit of what can be
represented as a floating point number.

Looking at this from the "what changed" point of view: I don't believe
that either the code (scm_c_round() in libguile/numbers.c) or the test
(test-suite/standalone/test-round.c) has changed significantly since
2004.  As far as Debian is concerned, therefore, I would have expected
to see exactly the same m68k build failure for 1.8.1+1-4 (the current
stable version) and 1.8.4+1.2 (current testing).  But I haven't been
able to find any build logs to confirm or deny that.

Regards,
        Neil




  parent reply	other threads:[~2008-08-12 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wsjgnvp3.fsf@gnu.org>
2008-07-25 10:05 ` Summer holidays Neil Jerram
     [not found] ` <49dd78620807280231g3ab15246l2cb9fd49025dcfa7@mail.gmail.com>
     [not found]   ` <49dd78620807290108p63704f96v7f0efc139be66112@mail.gmail.com>
     [not found]     ` <87sktsi4tf.fsf@raven.defaultvalue.org>
     [not found]       ` <877ib1mfdu.fsf@raven.defaultvalue.org>
     [not found]         ` <49dd78620808040339xacc8e1dm344af6a93350fbc8@mail.gmail.com>
     [not found]           ` <877iaowf9h.fsf@raven.defaultvalue.org>
     [not found]             ` <87sktcqq4n.fsf@raven.defaultvalue.org>
     [not found]               ` <49dd78620808110158i2fd25f10u257aa0cbc0d74ae5@mail.gmail.com>
     [not found]                 ` <49dd78620808120737t68d167e4ob2768e88804da22c@mail.gmail.com>
2008-08-12 20:36                   ` Neil Jerram [this message]
     [not found]                   ` <87hc9pizmy.fsf@raven.defaultvalue.org>
2008-08-13  7:36                     ` Just in case Neil Jerram

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49dd78620808121336l6604a5e1m9d0e531c24b5580b@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=rlb@defaultvalue.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).