Is there any way to check if a number that is inputted for factoring is already listed in the factored.dat file, and if so verify the listed factors and if they are valid automatically output them without starting the factoring from scratch?

Strange SIQS-related crash. What's causing it?
 

Why does this number crash YAFU 2.06?

[code]72201646132199873461502083685639136119064441143576829474934045444051626750298129[/code]Here's the output to cmd:

[code]C:\Numbers\yafu-master>yafu 72201646132199873461502083685639136119064441143576829474934045444051626750298129
Applying tune_info entry for WIN64 - Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz


YAFU Version 2.06
Built with Microsoft Visual Studio 1922
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
Detected L1 = 32768 bytes, L2 = 8388608 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 =======
===============================================================

>> fac: factoring 72201646132199873461502083685639136119064441143576829474934045444051626750298129
fac: using pretesting plan: deep
fac: using tune info for qs/gnfs crossover
input from file = 2204163746040422113335335630634510483693477785822927479792844125899447775787592580144299824908196479
input to yafu = 72201646132199873461502083685639136119064441143576829474934045444051626750298129
div: primes less than 10000
fmt: 1000000 iterations
93%fmt: performed 23 perfect square checks
rho: x^2 + 3, starting 1000 iterations on C80
rho: x^2 + 2, starting 1000 iterations on C80
rho: x^2 + 1, starting 1000 iterations on C80
nfs: searching for brent special forms...

<snip>

nfs: snfs form detection took 0.934170 seconds
nfs: couldn't find special form
pm1: starting B1 = 150K, B2 = gmp-ecm default on C80
pm1: Process took 0.0170 seconds.
pm1: found c36 factor = 256618303712888684191205903598313519
fac: setting target pretesting digits to 15.00
fac: estimated sum of completed work is t0.00
fac: work done at B1=2000: 0 curves, max work = 30 curves
fac: 30 more curves at B1=2000 needed to get to t15.00

Composite result found, starting re-factorization
fac: factoring 256618303712888684191205903598313519
fac: using pretesting plan: normal
fac: no tune info: using qs/gnfs crossover of 95 digits
fac: no tune info: using qs/snfs crossover of 75 digits
div: primes less than 10000
fmt: 1000000 iterations
rho: x^2 + 3, starting 1000 iterations on C36
rho: x^2 + 2, starting 1000 iterations on C36
rho: x^2 + 1, starting 1000 iterations on C36

starting SIQS on c36: 256618303712888684191205903598313519

C:\Numbers\yafu-master>[/code]factor.log:

[code]01/11/22 17:09:26,
01/11/22 17:09:26, ****************************
01/11/22 17:09:26, Starting factorization of 72201646132199873461502083685639136119064441143576829474934045444051626750298129
01/11/22 17:09:26, using pretesting plan: deep
01/11/22 17:09:26, using tune info for qs/gnfs crossover
01/11/22 17:09:26, ****************************
01/11/22 17:09:26, rho: x^2 + 3, starting 1000 iterations on C80
01/11/22 17:09:26, rho: x^2 + 2, starting 1000 iterations on C80
01/11/22 17:09:26, rho: x^2 + 1, starting 1000 iterations on C80
01/11/22 17:09:27, pm1: starting B1 = 150K, B2 = gmp-ecm default on C80
01/11/22 17:09:27, c36 = 256618303712888684191205903598313519
01/11/22 17:09:27, current ECM pretesting depth: 0.00
01/11/22 17:09:27, scheduled 30 curves at B1=2000 toward target pretesting depth of 15.00
01/11/22 17:09:27, prp45 = 281358130295261309435186241678306806768864191
01/11/22 17:09:27,
01/11/22 17:09:27, ****************************
01/11/22 17:09:27, Starting factorization of 256618303712888684191205903598313519
01/11/22 17:09:27, using pretesting plan: normal
01/11/22 17:09:27, no tune info: using qs/gnfs crossover of 95 digits
01/11/22 17:09:27, no tune info: using qs/snfs crossover of 75 digits
01/11/22 17:09:27, ****************************
01/11/22 17:09:27, rho: x^2 + 3, starting 1000 iterations on C36
01/11/22 17:09:27, rho: x^2 + 2, starting 1000 iterations on C36
01/11/22 17:09:27, rho: x^2 + 1, starting 1000 iterations on C36
01/11/22 17:09:27, final ECM pretested depth: 0.00
01/11/22 17:09:27, scheduler: switching to sieve method
01/11/22 17:09:27, starting SIQS on c36: 256618303712888684191205903598313519
01/11/22 17:09:27, random seed: 3836357694855539672
[/code]Error message (Event Viewer):

[code]Faulting application name: yafu.exe, version: 0.0.0.0, time stamp: 0x611c3335
Faulting module name: yafu.exe, version: 0.0.0.0, time stamp: 0x611c3335
Exception code: 0xc0000005
Fault offset: 0x000000000000be19
Faulting process id: 0x27fc
Faulting application start time: 0x01d80737e57dff6c
Faulting application path: C:\Numbers\yafu-master\yafu.exe
Faulting module path: C:\Numbers\yafu-master\yafu.exe
Report Id: dfd85e6a-3fcc-4269-b47c-a3f8a2a1eece
Faulting package full name:
Faulting package-relative application ID: [/code]

v2.08
 

Version 2.08 now available with a few bugfixes.

[QUOTE=Stargate38;597688]Why does this number crash YAFU 2.06?

[code]72201646132199873461502083685639136119064441143576829474934045444051626750298129[/code][/QUOTE]

Thanks, this should be fixed now in version 2.08.

[QUOTE=bsquared;599720]Version 2.08 now available with a few bugfixes.



Thanks, this should be fixed now in version 2.08.[/QUOTE]

I downloaded 2.08 and I've got the same problem I had with 2.07 when that was first available, in that it would appear that the Windows .exe file is missing a few bytes:

[CODE]JANELT3 C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.08 > yafu-x64


YAFU Version 2.08
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
Could not parse yafu.ini from C:\Users\Jane\Documents\Maths\yafu\Versions\yafu-2.08

===============================================================
======= 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.08 >[/CODE]

[QUOTE=bsquared;575505]It has been so long since a new windows executable and trunk code update have been released that I thought I might as well bump the version number to 2.....[/QUOTE]

I used to be able to run the older versions, but this, I doubt I would ever learn how. It searches for things I have no idea about. The help documentation may be helpful, but I cannot find it. Oh well. No big deal.

New Bug ?
 

Hello, we tested the number N with YAFU, YAFU can not finished this tasks.


N=factor((6414^13+17)*29848923566697359898432276895208549089323990314369)


The version is these here: [URL]https://github.com/bbuhrow/yafu/blob/master/bin/x64/Release/yafu-x64.exe[/URL]

[QUOTE]
poly_stage1_run done
**** finished poly work in thread 4
elapsed time: 21.6177 seconds (148 second deadline); poly select done
nfs: commencing algebraic side lattice sieving over range: 887500 - 890000
nfs: commencing algebraic side lattice sieving over range: 870000 - 872500
nfs: commencing algebraic side lattice sieving over range: 880000 - 882500
nfs: commencing algebraic side lattice sieving over range: 872500 - 875000
nfs: commencing algebraic side lattice sieving over range: 882500 - 885000
nfs: commencing algebraic side lattice sieving over range: 875000 - 877500
nfs: commencing algebraic side lattice sieving over range: 885000 - 887500
nfs: commencing algebraic side lattice sieving over range: 877500 - 880000
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der
konnte nicht gefunden werden.
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der Befehl ".." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
fopen error: No such file or directory
could not open rels0.dat for reading

E:\YAFU_2022>
[/QUOTE]





greetings

[QUOTE=Cybertronic;601659]Hello, we tested the number N with YAFU, YAFU can not finished this tasks.[/QUOTE]Do you have these settings properly configured in [c]yafu.ini[/c]?[quote]ggnfs_dir=E:\YAFU_2022\ggnfs-bin\
ecm_path=E:\YAFU_2022\ecm\ecm.exe[/quote]And of course have the [url=https://download.mersenne.ca/GGNFS]GGNFS[/url] and [url=https://download.mersenne.ca/GMP-ECM]ECM[/url] files where you have it configured?

Ah ! You mean, YAFU need this helperprograms and it was not found ? Okay thx!

For what it's worth I just tried it in both v1.34.5 and v2.07 and it worked fine:[code]prp50 = 29848923566697359898432276895208549089323990314369
prp50 = 31093987719382384075336599461075903930020102201361[/code]

After upgrading to the current git version from 2.05, I got a way lower QS/NFS (98.4 to 93.1 digits) crossover. It does not look like NFS got magically faster, but QS slower. Unfortunately, I overwrote my old build. Stupid me.

Instead, after observing the above, I tried to build the current version with clang (AOCC version). Is there any chance we could figure out how to do this? At least gmp, msieve, ytools and ysieve built without problems. The first problem occured while compiling yafu and was:
[CODE]include/monty.h:145:19: error: invalid input constraint '0ULL' in asm
: "1"(c), "0ULL"(0), "r"(n));[/CODE]
I am not sure what clang is expecting instead here.

I committed a fix for the ULL issue, a silly copy/paste thing that I'm surprised gcc/icc doesn't flag. As for it being slower, are you building with the right options for your cpu? If you have AVX-512 then use:
NFS=1 USE_AVX2=1 USE_BMI2=1 SKYLAKEX=1