From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: GMP bignum results using double cells.
Date: Thu, 27 Feb 2003 11:16:52 -0600 [thread overview]
Message-ID: <87u1epmynv.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <8765r5oesl.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 27 Feb 2003 10:43:06 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
>> Do we need to define scm_t_big_mpz in numbers.h? Couldn't it just be
>> an declared-but-undefined struct there? Like
>
> Possibly. In the first pass, I was just matching what the other types
> did, but this will probably work. I'll try it.
Ahh, that's why -- in gc-card.c, we have to call mpz_clear
(SCM_I_BIG_MPZ (x)). I'd put the direct call in there just for
efficiency, and I also used direct manipulations in a few other places
(dealing with the ipv6 addresses and random number generation I
think).
So would you prefer: SCM_CELL_ADDR_1, putting the scm_t_big_mpz in
numbers.h, or just adding functions to the scm_i_big interface for any
non-numbers.c usages of bignums, even libguile internal ones. The
latter would of course have more overhead, but it might not be
enough to be significant.
--
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-27 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 6:28 GMP bignum results using double cells Rob Browning
2003-02-26 21:54 ` Kevin Ryde
2003-02-27 1:27 ` Rob Browning
2003-02-28 22:45 ` Kevin Ryde
2003-02-27 13:33 ` Marius Vollmer
2003-02-27 16:43 ` Rob Browning
2003-02-27 17:16 ` Rob Browning [this message]
2003-02-27 17:46 ` Marius Vollmer
2003-02-27 17:55 ` Rob Browning
2003-03-01 13:43 ` Marius Vollmer
2003-03-02 0:52 ` Rob Browning
2003-03-02 1:40 ` 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=87u1epmynv.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).