From: "Mikael Djurfeldt" <mdjurfeldt@gmail.com>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Subject: Re: Problem with random numbers on the EM64T platform
Date: Sun, 19 Feb 2006 17:36:08 +0100 [thread overview]
Message-ID: <66e540fe0602190836t56a9557du9422bfe1b923ffef@mail.gmail.com> (raw)
In-Reply-To: <66e540fe0602180749r34d90071jd5e47851682eb567@mail.gmail.com>
On 2/18/06, Mikael Djurfeldt <mdjurfeldt@gmail.com> wrote:
> I've compiled CVS HEAD on the EM64T platform (Xeon processor).
>
> (random:uniform) gives results outside the intended interval [0,1[.
I've now fixed this in CVS HEAD:
2006-02-19 Mikael Djurfeldt <mdj@neurologic.cc>
* random.c: Test for SCM_HAVE_T_UINT64 instead of
SCM_HAVE_T_INT64.
(scm_i_uniform32, scm_i_uniform32, scm_i_init_rstate): Use
scm_t_uint64 and scm_t_uint32 instead of scm_t_int64 and
scm_t_int32.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-02-19 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 15:49 Problem with random numbers on the EM64T platform Mikael Djurfeldt
2006-02-19 16:36 ` Mikael Djurfeldt [this message]
2006-02-20 23:08 ` Marius Vollmer
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=66e540fe0602190836t56a9557du9422bfe1b923ffef@mail.gmail.com \
--to=mdjurfeldt@gmail.com \
--cc=djurfeldt@nada.kth.se \
/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).