From: Rob Browning <rlb@defaultvalue.org>
Subject: Nearly finished (re)integrating GMP for bignums.
Date: Wed, 12 Feb 2003 10:07:29 -0600 [thread overview]
Message-ID: <87heb9pjni.fsf@raven.i.defaultvalue.org> (raw)
I've finished much of the work (re-doing it after losing my previous
effort :<), but I still have to figure out how to handle the
ipv6->bignum code in sockets.c, and how to deal with random.c. In the
former, raw operations are used. I'm tempted to just rewrite the
computation as mathematical operations on the input char[] items
rather than trying to optimize it with larger memcpy operations.
Thoughts? One thing I note is that it looks like the code presumes
that an INUM will always fit into a 32bit integer. Do we guarantee
that, or is there the possibility we might allow 64bit inums? I
wasn't sure which guarantees we planned to make.
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?
After I get the system to compile, I'll then be adding tests (and
probably benchmarks). I don't want to commit it until I feel fairly
confident its correct, and hopefully have some sense of the relative
performance.
--
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 reply other threads:[~2003-02-12 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 16:07 Rob Browning [this message]
2003-02-12 16:26 ` Nearly finished (re)integrating GMP for bignums 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
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=87heb9pjni.fsf@raven.i.defaultvalue.org \
--to=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).