From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.de>
Subject: Re: Nearly finished (re)integrating GMP for bignums.
Date: Wed, 12 Feb 2003 12:57:34 -0600 [thread overview]
Message-ID: <87y94lnx7l.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy77kc52yik.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Wed, 12 Feb 2003 18:34:59 +0100")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> 2. What do you mean by a "good" RNG? I'd say it is good if it is
> fast. Our generator is fast.
I wonder how fast the GMP RNGs are (I currently have no idea).
> Ideally, the bignum code would use the pluggable source of random
> bits in random.c and the GMP generators would be provided as
> optional plugins for random.c. Rob, is this possible?
I'm not sure yet -- what I was considering was if (in the short term)
I can just replace the one BIGNUM based chunk of code in there with
calls to manipulate GMPs (or just calls to scm_i_big* functions). At
the very least, the code has to be changed so that it doesn't try to
manipulate BIGDIG stuff directly anymore since all the implementation
specific stuff is gone.
--
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-02-12 18:57 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 [this message]
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
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=87y94lnx7l.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).