New revision (513)

+ added a bunch of protection against trying to close a NULL file
+ vecPPM1: corrected METHOD strings in gmp-ecm resume files (should be P+1 and P-1)
+ vecPPM1: only output active vector lanes to resume file
+ fixed op/of/ou file output
+ update yafu-x64.exe (version 2.01)

[QUOTE=bsquared;577714]If you use session.log (active by default), then the version and build info appears in there. Date stamps can be correlated to factor.log output, should that be needed. Is that enough? Feedback welcome.

[CODE]
05/05/21 09:31:52, =====================================
05/05/21 09:31:52, System/Build Info:
05/05/21 09:31:52, YAFU Version 2.0
05/05/21 09:31:52, Built with Intel Compiler 1910
05/05/21 09:31:52, Using GMP-ECM 7.0.4, Powered by GMP 6.2.0
05/05/21 09:31:52, detected Intel(R) Xeon(R) Gold 6254 CPU @ 3.10GHz
detected L1 = 32768 bytes, L2 = 25952256 bytes, CL = 64 bytes
05/05/21 09:31:52, using 1 random witness for Rabin-Miller PRP checks
05/05/21 09:31:52, Cached 664579 primes: max prime is 9999991

05/05/21 09:31:52, Random seed: 11617470479886605489
05/05/21 09:31:52, Processing: factor(rsa(300))
05/05/21 09:32:19, Result : 1
[/CODE][/QUOTE]

This doesn't work for me; here is an extract from my file where I changed over to the new version.
[CODE]05/04/21 12:08:34 v1.34.5 @ JANELT3, System/Build Info:
Using GMP-ECM 6.3, Powered by GMP 5.1.1
cached 78498 primes. pmax = 999983
detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
measured cpu frequency ~= 2475.649860
using 20 random witnesses for Rabin-Miller PRP checks

05/04/21 12:08:34 v1.34.5 @ JANELT3, New random seeds: 1781426379, 516928000

05/04/21 12:08:34 v1.34.5 @ JANELT3, Processing expression: factor(1659483557006307984471893306873906022613514850665507820966965932477080093622434599791524757051092471754318679916001651)

05/04/21 12:09:35 v1.34.5 @ JANELT3, System/Build Info:
Using GMP-ECM 6.3, Powered by GMP 5.1.1
cached 78498 primes. pmax = 999983
detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
measured cpu frequency ~= 2479.754400
using 20 random witnesses for Rabin-Miller PRP checks

05/04/21 12:09:35 v1.34.5 @ JANELT3, New random seeds: 3193960914, 2134336360

05/04/21 12:09:35 v1.34.5 @ JANELT3, Processing expression: factor(52602411030795521624144403777822648860941742757032930290383906072720236420065195931310579378461645290846309381)

05/04/21 19:26:51, =====================================
05/04/21 19:26:51, System/Build Info:
05/04/21 19:26:51, detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
05/04/21 19:26:51, using 1 random witness for Rabin-Miller PRP checks
05/04/21 19:26:51, Cached 664579 primes: max prime is 9999991

05/04/21 19:26:51, Random seed: 6005946639089262856
05/04/21 19:26:51, Processing: factor(1552430857998742529411783620991507130911583093310701152041889198802805355311288815262351476779178174815899176986625121)
05/04/21 19:26:52, Result : 1552430857998742529411783620991507130911583093310701152041889198802805355311288815262351476779178174815899176986625121
[/CODE]

Also
[QUOTE]+ fixed op/of/ou file output
+ update yafu-x64.exe (version 2.01)[/QUOTE]

Wow! That was quick. Thank you.

[QUOTE=BudgieJane;577727]This doesn't work for me; here is an extract from my file where I changed over to the new version.
[/QUOTE]

Is that true even for the new .exe I just posted to github? It's possible the previous .exe didn't log that info, true, but this one should.

[QUOTE=bsquared;577729]Is that true even for the new .exe I just posted to github? It's possible the previous .exe didn't log that info, true, but this one should.[/QUOTE]

I'll have to come back to you on that, as I've got the previous version running at the moment.

It won't run. What have I done wrong? I tried to run it in my application, with no luck, so next I tried to run it in its own directory. It starts up and gets as far as Welcome to YAFU (which tells me I've got the right executable), then it exits with no messages at all. I would expect something from my last attempt, as I'm not directing the log or the output to files.

Here's what shows on my Command Prompt window, with subsequent attempts passing fewer parameters to the program:

[CODE]JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.0 > yafu-x64 factor(209148044825831719227566657932036925083843946561624836465070487458386685769672561025528073586991964435529919531) -forceDLP -v -v -v -silent -R -logfile io\log15.txt -of io\out15.txt

JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.0 > yafu-x64 factor(209148044825831719227566657932036925083843946561624836465070487458386685769672561025528073586991964435529919531) -forceDLP -v -R -logfile io\log15.txt -of io\out15.txt
Applying tune_info entry for WIN64 - Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz


YAFU Version 2.01
Built with Microsoft Visual Studio 1922
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
Detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
======= bbuhrow@gmail.com =======
======= Type help at any time, or quit to quit =======
===============================================================

>>
JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.0 > yafu-x64 -logfile io\log01.txt -of io\out01.txt


YAFU Version 2.01
Built with Microsoft Visual Studio 1922
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
Detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
======= bbuhrow@gmail.com =======
======= Type help at any time, or quit to quit =======
===============================================================

>>
JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.0 > yafu-x64


YAFU Version 2.01
Built with Microsoft Visual Studio 1922
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
Detected L1 = 32768 bytes, L2 = 6291456 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
======= bbuhrow@gmail.com =======
======= Type help at any time, or quit to quit =======
===============================================================

>>
JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.0 >[/CODE]

I forgot to add session.log has been set up, but contains 0 bytes.

I don't know... hmm. Do you have session.log open somewhere? If so close it... maybe that would happen if session.log exists but isn't writable. I don't know that's my best guess so far.

[QUOTE=bsquared;577753]I don't know... hmm. Do you have session.log open somewhere? If so close it... maybe that would happen if session.log exists but isn't writable. I don't know that's my best guess so far.[/QUOTE]

I went through all that, no luck.

So I thought I'd download it again, but this time instead of just downloading the executable, I downloaded the whole zip file, and set it up in its own directory among the versions. Again no luck.

When I put the version 2.01 executable into the 2.0 directory, I didn't overwrite the 2.0 version. So I've now renamed the files back again and run the 2.0 exe. I factored 26^65-19^65 successfully (no point on doing really big numbers just for testing).

I noticed that the version 2.0 executable is 2,320,384 bytes, whereas 2.01 is 2,087,424 bytes. Is that size difference reasonable? Would you expect the size of the executable to decrease? [Please forgive me for teaching my granny to suck eggs!]

I rebuilt everything and re-uploaded yafu-x64.exe. Everything has worked for me on three different intel windows machines... let me know what you find. [STRIKE]And maybe give me some more details on your processor if it doesn't work.[/STRIKE]

edit, nevermind, I see you posted those details already.

First, the good news: it no longer crashes.
Second, the good news: the -of parameter works.
Third: the version number appears in the session.log file.

[QUOTE=bsquared;577799]I rebuilt everything and re-uploaded yafu-x64.exe. Everything has worked for me on three different intel windows machines... let me know what you find. [STRIKE]And maybe give me some more details on your processor if it doesn't work.[/STRIKE]

edit, nevermind, I see you posted those details already.[/QUOTE]

Feedback: the new yafu-x64.exe is 2,318,848 bytes as opposed to the 2,007,424 bytes it was yesterday, which suggests that somehow or other something was missed in the earlier build, and your rebuild has fixed it.

And finally, the good news: I am happy with this. Thank you for your help.

Nothing but good news, I am happy too.

Possible bug in SIQS
 

When I try to factor this number, YAFU gets stuck, and just sits there using up my RAM:

[code]05/06/21 11:38:27,
05/06/21 11:38:27, ****************************
05/06/21 11:38:27, Starting factorization of 22483602822411223334855029666009218022270527893974405884054854479042089269501959654874976198718241182261793523272124947
05/06/21 11:38:27, using pretesting plan: deep
05/06/21 11:38:27, using tune info for qs/gnfs crossover
05/06/21 11:38:27, ****************************
05/06/21 11:38:27, rho: x^2 + 3, starting 1000 iterations on C119
05/06/21 11:38:27, prp9 = 405125431
05/06/21 11:38:27, rho: x^2 + 3, starting 1000 iterations on C110
05/06/21 11:38:27, prp10 = 3464048167
05/06/21 11:38:27, rho: x^2 + 3, starting 1000 iterations on C101
05/06/21 11:38:28, rho: x^2 + 2, starting 1000 iterations on C101
05/06/21 11:38:28, rho: x^2 + 1, starting 1000 iterations on C101
05/06/21 11:38:28, pm1: starting B1 = 150K, B2 = gmp-ecm default on C101
05/06/21 11:38:28, current ECM pretesting depth: 0.00
05/06/21 11:38:28, scheduled 30 curves at B1=2000 toward target pretesting depth of 33.67
05/06/21 11:38:28, Finished 30 curves using GMP-ECM method on C101 input, B1=2k, B2=gmp-ecm default
05/06/21 11:38:28, current ECM pretesting depth: 15.18
05/06/21 11:38:28, scheduled 74 curves at B1=11000 toward target pretesting depth of 33.67
05/06/21 11:38:30, Finished 74 curves using GMP-ECM method on C101 input, B1=11k, B2=gmp-ecm default
05/06/21 11:38:30, current ECM pretesting depth: 20.24
05/06/21 11:38:30, scheduled 214 curves at B1=50000 toward target pretesting depth of 33.67
05/06/21 11:38:38, Finished 214 curves using GMP-ECM method on C101 input, B1=50k, B2=gmp-ecm default
05/06/21 11:38:38, pm1: starting B1 = 3750K, B2 = gmp-ecm default on C101
05/06/21 11:38:39, current ECM pretesting depth: 25.33
05/06/21 11:38:39, scheduled 430 curves at B1=250000 toward target pretesting depth of 33.67
05/06/21 11:39:37, Finished 430 curves using GMP-ECM method on C101 input, B1=250k, B2=gmp-ecm default
05/06/21 11:39:37, pm1: starting B1 = 15M, B2 = gmp-ecm default on C101
05/06/21 11:39:39, current ECM pretesting depth: 30.45
05/06/21 11:39:39, scheduled 582 curves at B1=1000000 toward target pretesting depth of 33.67
05/06/21 11:44:26, Finished 582 curves using GMP-ECM method on C101 input, B1=1M, B2=gmp-ecm default
05/06/21 11:44:26, final ECM pretested depth: 33.67
05/06/21 11:44:26, scheduler: switching to sieve method
05/06/21 11:44:26, starting SIQS on c101: 16021105361578943740813272184915150830500965883014131722097771902253017316544048423666824742984602611
05/06/21 11:44:26, random seed: 2350092192
[/code]

Stdout:

[code]starting SIQS on c101: 16021105361578943740813272184915150830500965883014131722097771902253017316544048423666824742984602611
static memory usage:
assigning tdiv_medprimes_32k_avx2 ptr
assigning tdiv_LP_avx2 ptr
assigning resieve_medprimes_32k_avx2 ptr
assigning med_sieveblock_32k_avx2 ptr
assigning nextRoots_32k_sse41 ptr
initial cycle hashtable: 16777216 bytes
initial cycle table: 160000 bytes
factor base: 2452160 bytes
fb bounds
small: 1024
SPV: 36
10bit: 88
11bit: 160
12bit: 296
13bit: 528
32k div 3: 688
14bit: 984
15bit: 1760
med: 2912
large: 16704
large_x2: 31670
all: 122608
start primes
SPV: 251
10bit: 1063
11bit: 2153
12bit: 4177
13bit: 8273
32k div 3: 11083
14bit: 16417
15bit: 32803
med: 57593
large: 393161
large_x2: 786431
all: 3423347
05/06/21 11:44:26, multiplying 0 primes from 3423347 to 1398101[/code]

During this process, the CPU usage suggests only 1 out of 8 threads are running. Looks like a memory leak. Same thing happens with 2.01.