_mp_alloc vs ALLOC

bodrato at mail.dm.unipi.it bodrato at mail.dm.unipi.it
Sat Jun 2 21:21:16 CEST 2012


Il Sab, 2 Giugno 2012 6:32 pm, Niels Möller ha scritto:
> Torbjorn Granlund <tg at gmplib.org> writes:

>> I thought avoiding the copying was a good idea, but this thread has made
>> me less sure.
> I guess some benchmarks are needed here.

That's why I did not propose to change the behavior of the library, but to
"mark" the possible uses with a different macro. So that we can count how
many times, and see where, we might need the no-copy-realloc.
After that we can decide: to change or not to change. And the change can
be: let the default unchanged, allowing the user to set its own function.

> I think "Obsolete, always zero" would be less confusing than "sometimes

"always" forces the change more than "sometimes" does.

>> make a subpage to the GMP devel web pages, "Things the developers
>> think are broken in GMP" with this list.
> I think that's a good idea. And I guess it might need a special section
> about "things some (but not all) developers think are broken"...

Only the second one is needed. Things that all developers think are broken
should be included in the page "planned improvements".



More information about the gmp-devel mailing list