Problems with sr2sieve on x86-64 Windows
 

There seems to be a problem with sieving above 2^51 (2250T) on Windows with all x86-64 sr2sieve executables. This will start to affect SoB/PSP soon.

I am looking into the problem but if it turns out to be related to bugs in the Linux->Windows cross compiler then there might not be a solution by the time SoB/PSP sieving reaches 2^51.

The only `fix' at the moment is to use the 32-bit (*-windows-x86.zip) executable on Windows.

What are the symptoms? How did you discover this?

In the meantime, I urge all 64-bit Windows users to immediately change to the 32-bit Windows executable.

[QUOTE=Joe O;120270]What are the symptoms? How did you discover this?

In the meantime, I urge all 64-bit Windows users to immediately change to the 32-bit Windows executable.[/QUOTE]

The main symptom is a crash (access violation) soon after starting. It was first reported by Bryan at RieselSieve who was trying to get a 64-bit Windows BOINC client working. It has since been confirmed by others.

The problem seems to have been present in all the x86-64 Windows sr2sieve executables since I first started making them at version 1.5.21, but has gone unnoticed because it seems only to affect the code used for sieving p-ranges above 2^51, only RieselSieve is currently sieving that deep and they only use the 32-bit Windows executable.

The problem with the Windows x86-64 executable seem to be fixed in sr2sieve version 1.6.16.

If anyone running 64-bit Windows can help with testing, what would be really useful is to reserve a current range of about 100G or so, then add the switchs `-D duplicates.txt --no-sse2' to the normal command line for manual sieving. Send me a copy of both the factors*.txt and duplicates.txt files, and I will check the range using the Linux executable. My email address is in README.txt included with sr2sieve.

sr2sieve 1.6.16 on Windows x86-64 is producing correct results. Thanks to those who helped with testing.