In order to bring the Windows build into closer alignment with that on
Linux, I have renamed all references to 'amd64' in the Windows build
files to 'k8'. I have done this in preparation for adding a new x64
'nehalem' build project for Windows.
In order to reduce the complexity of the Windows build projects, I am
now inclined to split the mpir Windows build solution into two
separate build solutions, the first for 32-bit builds and the second
for 64-bit builds. I would be interested to hear people's views on
this.
Right now the Windows 32-bit builds are being maintained but they are
not being actively developed. What this means is that new C source
code files are added when necessary but there is no new 32-bit
assembler code to take advantage of new architectures. So the Windows
performance of MPIR on modern 32-bit systems is not what it could (or
should) be.
If there is still a strong interest in 32-bit performance, we need
volunteers to maintain and develop this apsect of MPIR on Windows as I
don't have the time (or the inclination) to do it. Is 32-bit
performance on Windows still important and, if it is, is anyone
willing to volunteer to take on the work involved?
best regards to all,
Brian Gladman
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
