From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.de>
Subject: Re: Nearly finished (re)integrating GMP for bignums.
Date: Thu, 06 Mar 2003 11:31:26 -0600 [thread overview]
Message-ID: <87n0k8v1u9.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy74r6k3865.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Mon, 03 Mar 2003 14:13:06 +0100")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> It does this by allocating a bignum b with as many base 65536 digits
> as m, filling b with random bits (in 32 bit chunks) up to the most
> significant 1 in m, and, finally checking if the resultant b is too
> large (>= m). If too large, we simply repeat the process again.
> (It is important to throw away all generated random bits if b >= m,
> otherwise we'll end up with a distorted distribution.)
It looks like the old code handled 16-bit chunks at a time. I just
wanted to make sure it was OK to go ahead and use the full "unsigned
long" random_bits range per-chunk instead if that works out better.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-03-06 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 16:07 Nearly finished (re)integrating GMP for bignums Rob Browning
2003-02-12 16:26 ` Marius Vollmer
2003-02-12 17:32 ` Rob Browning
2003-02-12 17:34 ` Mikael Djurfeldt
2003-02-12 18:57 ` Rob Browning
2003-02-12 21:13 ` Rob Browning
2003-02-12 23:00 ` Kevin Ryde
2003-02-27 5:11 ` Rob Browning
2003-03-03 13:13 ` Mikael Djurfeldt
2003-03-03 13:21 ` Mikael Djurfeldt
2003-03-06 17:31 ` Rob Browning [this message]
2003-03-06 18:13 ` Mikael Djurfeldt
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=87n0k8v1u9.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=mvo@zagadka.de \
/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).