Yay!

[CODE]
Processing result: M( 26206723 )C, 0x19fb046af3bf4bce, n = 1572864, CUDALucas v1.64
LL test successfully completes double-check of M26206723
[/CODE]

I saw I had 3 results this morning before leaving for job, two from 1.64 and one from 1.63, but could not report them (server was down, as everybody already know). No idea if they matched, and unfortunately, they will have to wait about 6 hours more, till I can reach that computer again. I will keep you informed about the result, in 6 hours.

When PrimeNet's down, you could use Mersenne-aries, because it has everything up to at least the day before.

[QUOTE=Dubslow;291936]When PrimeNet's down, you could use Mersenne-aries, because it has everything up to at least the day before.[/QUOTE]

Good point

[QUOTE=Dubslow;291936]When PrimeNet's down, you could use Mersenne-aries, because it has everything up to at least the day before.[/QUOTE]
Too late now. I will know it next time when we find another prime and the server will be down :P

Perfect, again
 

[CODE]Processing result: M( 29217869 )C, 0x1b92a9eb0e596b54, n = 1572864, CUDALucas v1.61
LL test successfully completes double-check of M29217869[/CODE]Switching to 1.64.

[QUOTE=apsen;291701]Got mismatch with 1.58 but had several err/increasing messages. Could be bad handling of that...[/QUOTE]

I have rerun 29198173 with 1.63 and got another mismatch. BTW no err messages on 1.63 side and residues matched between 1.58 and 1.63 up to the point of the first 1.58 err message.

Running 29027371 with 1.63 now. ETA 33 hours. Will rerun 29198173 with older version once 29027371 completes.

[QUOTE=aaronhaviland;291712]From the looks of things, all those errors can be tied back to the lack of definition of "BOOL" which I'm assuming is a pre-processor macro. (searching the internet...) on windows, you should probably "#include <WinDef.h>" at some point. I cannot confirm this due to a lack of a windows environment.[/QUOTE]

Agree on the BOOL issue. You need to be careful with includes so winsocks do not get included as it will prevent CudaLucas.cu from compiling. I believe BOOL is defined as int so you could just change the signature correspondingly.

I'll see what is the best way to fix that when I get to my VS computer.

[QUOTE=apsen;291995]
I'll see what is the best way to fix that when I get to my VS computer.[/QUOTE]

Actually that code does not need ifdef. You could compile it using unix semantics.

It is moving
 

[QUOTE=Brain;291986]Switching to 1.64.[/QUOTE]
Ehm, is it getter faster for you, too?
GTX 560 Ti @ clock speeds, 4.1/2.1 exe:
[CODE]1.58: M( 28652753 ), n = 1572864, CUDALucas v1.58: 6.03ms/Iter
1.61: M( 29217869 ), n = 1572864, CUDALucas v1.61: 5.73ms/Iter
1.64: M( 29013107 ), n = 1572864, CUDALucas v1.64: 5.08ms/Iter[/CODE]I thought 1.64 had 2% slowdown...
I like it. :wink:

[QUOTE=Brain;292075]I thought 1.64 had 2% slowdown...
:wink:[/QUOTE]
Only with the dirty switch. I love it WITH the switch, in fact... I prefer slower and safer.