From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: gmp issues (long)
Date: 25 Feb 2003 21:54:51 +0100 [thread overview]
Message-ID: <87y9446pyc.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87d6lhcnyn.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> The second (perhaps related) issue involves memory use. It turns out
> that an mpz_t, which is the GMP integer type, takes up a minimum of 12
> bytes (when an int is 4 bytes), and will always be more than that
> because that 12 bytes doesn't include any space for the actual digits.
I'm not so much worried about the size of an mpz_t but about the fact
that it requires an additional malloc. 12 bytes is just right for our
double cells, tho. So I would suggest making bignums a double cell
and putting the mpz_t structure into slots 1, 2, and 3. There should
be a test somewhere whether mpz_t really fits into this space. For
now we can just wait for this test to fail, I'd say.
This also removes the additional indirection.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-25 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 22:29 gmp issues (long) Rob Browning
2003-02-25 20:54 ` Marius Vollmer [this message]
2003-02-25 22:10 ` Rob Browning
2003-02-25 22:32 ` Marius Vollmer
2003-02-25 22:50 ` Rob Browning
2003-02-25 23:01 ` Marius Vollmer
2003-02-25 23:23 ` Rob Browning
2003-02-26 22:07 ` Kevin Ryde
[not found] <E18ndhx-0007Cm-00@monty-python.gnu.org>
2003-02-25 19:32 ` Stephen Compall
2003-02-25 20:08 ` Rob Browning
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=87y9446pyc.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).