From: nisse@lysator.liu.se (Niels Möller)
To: Mark H Weaver <mhw@netris.org>
Cc: 10519@debbugs.gnu.org, Torbjorn Granlund <tg@gmplib.org>
Subject: bug#10519: guile and (mini-)gmp
Date: Sat, 28 Jan 2012 10:49:03 +0100 [thread overview]
Message-ID: <nnty3gnomo.fsf@stalhein.lysator.liu.se> (raw)
In-Reply-To: <87aa5o2bm2.fsf@netris.org> (Mark H. Weaver's message of "Mon, 16 Jan 2012 05:19:33 -0500")
Mark H Weaver <mhw@netris.org> writes:
> It would be good if you could duplicate the `mp_set_memory_functions'
> interface in mini-gmp.
I'm looking into this. I found that the GMP interface has one awkward
feature: The current allocation size must be passed as an argument to
the free and realloc functions. See
http://gmplib.org/list-archives/gmp-devel/2012-January/002161.html
Does guile make any use of these size arguments? I'm considering having
mini-gmp *not* support this part of the allocation interface, and
instead always pass zero, for the sake of simplicity. I imagine that the
vast majority of users of the custom alloction interface ignore these
argments anyway, and store allocation size for each block elsewhere,
e.g., in some block header.
Regards,
/Niels
--
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.
next prev parent reply other threads:[~2012-01-28 9:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 21:22 bug#10519: guile and (mini-)gmp Niels Möller
2012-01-16 10:19 ` Mark H Weaver
2012-01-16 14:06 ` Niels Möller
2012-01-16 19:21 ` Mark H Weaver
2012-01-28 9:49 ` Niels Möller [this message]
2012-01-28 10:10 ` Mark H Weaver
2012-07-22 9:04 ` Ludovic Courtès
2012-02-03 13:40 ` Andy Wingo
2012-02-03 19:56 ` Niels Möller
2012-02-03 20:01 ` Torbjorn Granlund
2012-02-04 22:46 ` Ludovic Courtès
2012-07-22 9:00 ` Ludovic Courtès
2012-07-22 23:17 ` Niels Möller
2012-08-10 21:51 ` Ludovic Courtès
2012-08-11 9:37 ` Niels Möller
2012-08-11 19:46 ` Ludovic Courtès
2012-08-11 21:50 ` Niels Möller
2012-08-11 22:48 ` Ludovic Courtès
2013-03-02 20:04 ` Andy Wingo
2013-03-02 20:58 ` Mark H Weaver
2013-03-05 19:09 ` Mark H Weaver
2013-03-18 0:01 ` Mark H Weaver
2013-03-18 9:19 ` Ludovic Courtès
2013-03-26 8:17 ` Niels Möller
2013-03-27 17:00 ` Mark H Weaver
2016-10-27 12:29 ` Niels Möller
2016-11-10 19:56 ` Andy Wingo
2013-03-02 21:45 ` Niels Möller
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=nnty3gnomo.fsf@stalhein.lysator.liu.se \
--to=nisse@lysator.liu.se \
--cc=10519@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=tg@gmplib.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).