From: Stephen Compall <s11@member.fsf.org>
Subject: Re: gmp issues (long)
Date: Tue, 25 Feb 2003 13:32:17 -0600 [thread overview]
Message-ID: <200302251332.32383.s11@member.fsf.org> (raw)
In-Reply-To: <E18ndhx-0007Cm-00@monty-python.gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rob Browning wrote:
replace the _mp_size field with a short, since I doubt that we'd
ever be likely to overflow long data[MAX_SHORT] digits. (What was
the size limit, if any, on our old bignums?).
My first use of GMP in C (after the requisite playing around while
learning) was to try to build up a Godel number as an example in a
project involving semigroups I'm working on (OT). After creating one of
these numbers, I believe the memory usage of the mpz_t & friends was ~5
MB. While this was an abnormal case, it's still far off from 256k.
er....
- --
Stephen Compall - Also known as S11001001
DotGNU `Contributor' -- http://dotgnu.org
Jabber ID: sirian@theoretic.com
To be a hacker, one had to accept the philosophy that writing a
software program was only the beginning. Improving a program was the
true test of a hacker's skills.
-- Sam Williams, "Free as in Freedom"
According to Stallman, improving software programs was secondary to
building them in the first place.
-- Sam Williams, "Free as in Freedom"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+W8TF2AceYinZ4EgRAlZNAJ9P9F9eTsPNfc4jT2sT5eOuVfXmQwCffLBT
vXQI6o8La5tvIOsd07kuFgo=
=Et+6
-----END PGP SIGNATURE-----
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2003-02-25 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18ndhx-0007Cm-00@monty-python.gnu.org>
2003-02-25 19:32 ` Stephen Compall [this message]
2003-02-25 20:08 ` gmp issues (long) Rob Browning
2003-02-24 22:29 Rob Browning
2003-02-25 20:54 ` Marius Vollmer
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
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=200302251332.32383.s11@member.fsf.org \
--to=s11@member.fsf.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).