On 01/09/2012, James M. wrote:
> Thanks for the quick reply.
> Why the setting of the top bit first?
This is just to ensure sufficient memory is allocated.
> I will certainly look into the mpn functions for implementation, as I keep
> all handling of mpir and calculation of the morton numbers re
Thanks for the quick reply.
Why the setting of the top bit first?
I will certainly look into the mpn functions for implementation, as I keep
all handling of mpir and calculation of the morton numbers restricted to
the interior of a single class, even if it is tricky to get done I only
need to do
You are right, __GMP_MP_RELEASE was subsequently renamed
to __GNU_MP_RELEASE and thats what it is in the current GMP.
gap-4.5.5 only checks __GMP_MP_RELEASE if __GNU_MP_RELEASE is not defined
%-)
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" grou
On Saturday, 1 September 2012 12:28:25 UTC+1, Volker Braun wrote:
>
> No I really meant __GMP_MP_RELEASE! Though that might be a good question
> to ask the GMP developers. In any case, see
>
> http://gmplib.org/list-archives/gmp-commit/2010-January/000283.html
>
> for the commit.
>
> That is od
No I really meant __GMP_MP_RELEASE! Though that might be a good question to
ask the GMP developers. In any case, see
http://gmplib.org/list-archives/gmp-commit/2010-January/000283.html
for the commit.
On Saturday, September 1, 2012 8:20:59 AM UTC+1, Cactus wrote:
>
> Did you mean __GNU_MP_REL
On Monday, 27 August 2012 00:52:32 UTC+1, Volker Braun wrote:
>
> Starting with GMP 5.0.1 the version can also be gotten from the following
> macro in gmp.h (autogenerated from gmp-h.in):
>
> #define __GMP_MP_RELEASE (__GNU_MP_VERSION * 1 +
> __GNU_MP_VERSION_MINOR * 100 + __GNU_MP_VERSION_