From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Nearly finished (re)integrating GMP for bignums.
Date: Wed, 12 Feb 2003 11:32:05 -0600 [thread overview]
Message-ID: <874r79pfqi.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87r8adihxe.fsf@zagadka.ping.de> (Marius Vollmer's message of "12 Feb 2003 17:26:37 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> Aren't we already using 64 bits for scm_t_bits on some platforms (such
> as the Alpha and IA64)? Even if we don't, code should use
> SIZEOF_SCM_T_BITS, etc.
I'm not sure. It's been a while since I was messing around with guile
on a 64 bit platform (last time was porting issues on an alpha and
ia64). I can check...
>> With respect to random.c, we have a pluggable random number system,
>> and ATM the bignum randoms are computed using the
>> "get_32_random_bits()" function provided by the random state object.
>> However GMP has its own random number generators, including ones for
>> bignums. Any thoughts on how we should handle this?
>
> I think we should use the GMP generators unless they are not as good
> as ours. But I doubt that.
Hmm, OK. Well for now I may see about just trivially integrating the
gmp bignums into the current "plugin" system which only allows for a
generator to generate 32 random bits at a time. If I do, I'll list
"coming back later to see if we should rearrange things more
thoroughly" as a TODO item.
--
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 17:32 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 [this message]
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
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=874r79pfqi.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.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).