V24.12 release candidate 3

[Prime95]

Windows: ftp://mersenne.org/gimps/p95v2412.zip
Windows 64-bit: ftp://mersenne.org/gimps/p64v2412.zip
WinNT service: ftp://mersenne.org/gimps/winnt2412.zip
Linux: ftp://mersenne.org/gimps/mprime2412.tar.gz or
Static Linux: ftp://mersenne.org/gimps/sprime2412.tar.gz

This fixes a bug found in trial factoring MM31. The bug affected all exponents above 580 million.

Some out-of-date help file info was repaired.

[akruppa]

I get an "invalid compressed data--format violated" error when trying to uncompress sprime2412.tar.gz.

Alex

[nuutti]

tested 64-bit version. I was able to find these factors:
D: S340437/C66244893, M2147483647 has a factor: 295257526626031
[Fri Jun 24 21:41:29 2005]
UID: S340437/C66244893, M2147483647 has a factor: 87054709261955177

but later / higher program started to behave strangely. Here is my worktodo.ini:
AdvancedFactor=2147483647,2147483647,59,70

and program stopped to progress. Screenshot is included.

Yours,

Nuutti

[Prime95]

Originally Posted by akruppa

I get an "invalid compressed data--format violated" error when trying to uncompress sprime2412.tar.gz.

Linux binaries re-uploaded.

[akruppa]

Originally Posted by Prime95

Linux binaries re-uploaded.

Thanks, unpacks ok now.

Alex

PS. When doing Fullbench, Allbench On the Opteron 150, I get a lot of
Cannot initialize FFT code, errcode=1002
messages, but each FFT size seems to have one variant that works. Are those error messages normal? I don't remember seeing them with rc1.

[nuutti]

It found two factors:
[Sat Jun 25 00:18:40 2005]
M2147483647 has a factor: 295257526626031
[Sat Jun 25 00:19:00 2005]
M2147483647 has a factor: 87054709261955177


but it didn't found the third one:
[Sat Jun 25 02:59:43 2005]
M2147483647 no factor from 2^57 to 2^70, Wc1: 302ED088

(win xp 64-bit and Athlon 3,2 Ghz and 32-bit prime95 version 24.12 RC 3)

Yours,

Nuutti

[ATH]

Found 2 but not 3rd:
M2147483647 has a factor: 295257526626031
M2147483647 has a factor: 87054709261955177
M2147483647 no factor from 2^57 to 2^68, Wc1: 302ED088
on Windows XP SP2, P4 Northwood 2.4 Ghz.

[kjaget]

Not sure if this counts as a bug, but 24.12 is slower than 24.6 for exponents >= 1280K FFT size on my Celeron D machine (256K L2).

Thanks for the hard work on this upcoming release - my A64 system (and P3 for that matter) are enjoying the speed ups.

Intel(R) Celeron(R) CPU 2.53GHz
CPU speed: 3706.52 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 16 KB
L2 cache size: 256 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 15.042 ms.
Best time for 640K FFT length: 17.992 ms.
Best time for 768K FFT length: 21.886 ms.
Best time for 896K FFT length: 27.102 ms.
Best time for 1024K FFT length: 29.625 ms.
Best time for 1280K FFT length: 39.398 ms.
Best time for 1536K FFT length: 48.508 ms.
Best time for 1792K FFT length: 59.064 ms.
Best time for 2048K FFT length: 67.081 ms.

-------------------------------------------------------------

Intel(R) Celeron(R) CPU 2.53GHz
CPU speed: 3706.36 MHz
CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2
L1 cache size: 16 KB
L2 cache size: 256 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 32-bit version 24.12, RdtscTiming=1
Best time for 512K FFT length: 13.017 ms.
Best time for 640K FFT length: 16.995 ms.
Best time for 768K FFT length: 20.851 ms.
Best time for 896K FFT length: 25.712 ms.
Best time for 1024K FFT length: 28.494 ms.
Best time for 1280K FFT length: 40.293 ms.
Best time for 1536K FFT length: 50.786 ms.
Best time for 1792K FFT length: 64.826 ms.
Best time for 2048K FFT length: 72.109 ms.
Best time for 2560K FFT length: 85.316 ms.
Best time for 3072K FFT length: 106.302 ms.
Best time for 3584K FFT length: 131.413 ms.
Best time for 4096K FFT length: 147.715 ms.
Best time for 58 bit trial factors: 7.438 ms.
Best time for 59 bit trial factors: 7.446 ms.
Best time for 60 bit trial factors: 7.447 ms.
Best time for 61 bit trial factors: 7.460 ms.
Best time for 62 bit trial factors: 10.218 ms.
Best time for 63 bit trial factors: 10.211 ms.
Best time for 64 bit trial factors: 11.910 ms.
Best time for 65 bit trial factors: 11.979 ms.
Best time for 66 bit trial factors: 11.919 ms.
Best time for 67 bit trial factors: 11.862 ms.

[JHagerson]

I have a group of seven P II and P III machines that were doing double-checking, but because that is taking a very long time, I now have them assigned to get factoring assignments as they complete the double-checking assignments.

I upgraded one machine that was in the middle of a 2^68 factoring assignment from 24.11 to 24.12 RC3. When I restarted Prime95, that workstation immediately communicated with the server. The message on the screen was that no factors less than 2^67 had been found and gave a message checksum. Next, the workstation requested and received a new factoring assignment. Finally, the message on the screen said "resumed factoring of <new exponent> to 2^67." I checked WORKTODO.INI, and this new exponent is listed for factoring up to 2^62. Also, I checked my personal report on PrimeNet, and both the old and new numbers are assigned to this machine.

Please let me know what, if any, additional information you need. My P4 and Athlon 64 machines appreciate the new, more efficient, LL code.

Thank you very much.
John Hagerson

[smh]

Originally Posted by ATH

Found 2 but not 3rd:
M2147483647 has a factor: 295257526626031
M2147483647 has a factor: 87054709261955177
M2147483647 no factor from 2^57 to 2^68, Wc1: 302ED088
on Windows XP SP2, P4 Northwood 2.4 Ghz.

No 3rd one for me either.

Win. 2003 server. Pentium M 1,4GHz

[ET_]

Originally Posted by JHagerson

I have a group of seven P II and P III machines that were doing double-checking, but because that is taking a very long time, I now have them assigned to get factoring assignments as they complete the double-checking assignments.

If you have P II machines, you may as well check version 23.2: in many cases it is faster than verion 24 at factoring.

Also, note that in version 24.12 we'll have new factoinng breakeven points:
http://www.mersenneforum.org/showthread.php?t=4213

Luigi