On Tuesday 25 October 2011 10:43:38 Cactus wrote:
> The issue of 32/64-bit integers on Windows comes up regularly and, after
> the recent discussion, I have been wondering if there is a
> relatively easy implementation strategy.
>
> Since we already know from 64-bit Unix/Linux distributions that t
All the Windows x64 MPN assembler code now handles 64-bit integers (this was
not always the case).
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mpir-devel/-/Ju8pBgZqrNEJ
Do the internal library assembly functions work with 64 bit inputs, or
do they rely on extending 32 bit inputs?
On 25 October 2011 10:43, Cactus wrote:
> The issue of 32/64-bit integers on Windows comes up regularly and, after the
> recent discussion, I have been wondering if there is a
> relativ
The issue of 32/64-bit integers on Windows comes up regularly and, after the
recent discussion, I have been wondering if there is a
relatively easy implementation strategy.
Since we already know from 64-bit Unix/Linux distributions that the existing
*_ui and *_si functions work when signed and
