From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: gmp issues (long)
Date: Tue, 25 Feb 2003 16:50:36 -0600 [thread overview]
Message-ID: <87d6lgq8jn.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87smuc6lft.fsf@zagadka.ping.de> (Marius Vollmer's message of "25 Feb 2003 23:32:22 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> The way I understand things, GMP does not allocate the mpz_t's itself,
> right? Then you should be able to do things like
>
> SCM z = scm_double_cell (bignum_tag, 0, 0, 0);
> mpz_init (SCM_CELL_ADDR_1 (z));
> where SCM_CELL_ADDR_1 or something similar needs to be added to gc.h.
Hmm. Yep, that should work, and would be even faster.
Any easy way we could rearrange things to that we allocate a double
cell without initializing its fields at all (until the mpz_init),
i.e. save the redundant init to 0, without causing trouble with the
GC?
Anyway, thanks for the suggestion. I think I can get this working
pretty quickly so we can see how it fares. It'd be nice if it helps
out noticably on the performance side too...
--
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-25 22:50 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
2003-02-25 22:10 ` Rob Browning
2003-02-25 22:32 ` Marius Vollmer
2003-02-25 22:50 ` Rob Browning [this message]
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=87d6lgq8jn.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).