LLR Version 4.0.4 released.

[Jean Penné]

Hi All,

I uploaded to-day the new version 4.0.4 of LLR program on my personal site jpenne.free.fr
The main update in this version is described below :
I implemented the patch sent to me by Serge Batalov to process the special case of Phi(3,-b^n)=b^2n-b^n+1 using the pattern
(ABC $a^$b-$a^$c+1) for the input file. Using the modulus b^3n+1=(b^2n-b^n+1)(b^n+1) allows to benefit fully from the speed of DWT for the Pocklington algorithm.
Serge got recently the largest known non-Mersenne prime with this method.
And now, some minor updates :
- UseCharCode=1 is no more required to have a correct .res file.
- OLDRES64 is no more written by default.
- NextFFTifNearLimit option is now set to FALSE by default.

I hope this new version would help for further beautiful prime search successes!

Best Regards,
Jean

[rogue]

Have you addressed my concern with some primality tests taking an excessive amount of time?

[Jean Penné]

Originally Posted by rogue

Have you addressed my concern with some primality tests taking an excessive amount of time?

yes, but I have no accurate idea about that. Perhaps it may be due to the FFT length and/or DWT algorithm chosen by the gwnum code...

[Happy5214]

Was the NewPGen 0x100 mask removed (as stated in https://www.mersenneforum.org/showpo...95&postcount=5) for compatibility with the srsieve/srsieve2 family of sieve programs?

[Jean Penné]

Originally Posted by Happy5214

Was the NewPGen 0x100 mask removed (as stated in https://www.mersenneforum.org/showpo...95&postcount=5) for compatibility with the srsieve/srsieve2 family of sieve programs?

yes!

[storm5510]

I have an issue with cllr64 which existed in v4.0.3 as well.

I have to run it with Powershell functioning as a command prompt alternate. If I run it with in a command prompt console, the output text is not visible. It is just a black box. It stays this way after I stop it with Ctrl-C. I have to close it to reset it.

My OS is Windows 10 v22H2. IIRC, the behavior was the same with 21H2, and perhaps previous. Since I have not seen this mentioned before, it must be something unique to my setup. It uses the default font and text color.

[Jean Penné]

Originally Posted by storm5510

I have an issue with cllr64 which existed in v4.0.3 as well.

I have to run it with Powershell functioning as a command prompt alternate. If I run it with in a command prompt console, the output text is not visible. It is just a black box. It stays this way after I stop it with Ctrl-C. I have to close it to reset it.

My OS is Windows 10 v22H2. IIRC, the behavior was the same with 21H2, and perhaps previous. Since I have not seen this mentioned before, it must be something unique to my setup. It uses the default font and text color.

Perhaps did you forget to set the -d option in your command line?
This is required to see the output on the console window, for cllr on Windows as well as for llr on Linux or Mac OS.
Regards,

Jean

[storm5510]

Originally Posted by Jean Penné

Perhaps did you forget to set the -d option in your command line?
This is required to see the output on the console window, for cllr on Windows as well as for llr on Linux or Mac OS.
Regards,

Jean

I matched the font Powershell was using in the command prompt window -and- used the -d switch. Now, I can see it. Something I forgot to mention previously. Even though I could not see the text, I could see the cursor jumping around.

I have a pretty good idea of when this started. When I installed the GPU I have in this system now. An RTX 2080. However, none of the other prompt programs are effected, like srsieve2, mfaktc, gpuOwl, and so on.

Perhaps something in the ini file that duplicates the purpose of -d may be helpful.