20220530, 21:40  #342  
"James Heinrich"
May 2004
exNorthern Ontario
3,851 Posts 
Quote:


20220608, 13:52  #343 
Aug 2020
79*6581e4;3*2539e3
259_{16} Posts 
When I try to build yafu under Ubuntu with make NFS=1 USE_SSE41=1 USE_AVX=1 it quits with:
Code:
gcc g m64 DUSE_SSE2 DUSE_AVX2 DUSE_SSE41 mavx2 DUSE_SSE41 msse4.1 DUSE_NFS O2 fomitframepointer Wall I. Iinclude Itop/aprcl Itop/cmdParser Itop/ I../ysieve I../ytools I/usr/local/include I../msieve/zlib top/driver.o top/test.o factor/tune.o factor/autofactor.o top/cmdParser/cmdOptions.o top/cmdParser/calc.o o yafu lysiqs lyecm lynfs L. L../ysieve L../ytools L/usr/local/include L../msieve/ lmsieve lecm /usr/lib/x86_64linuxgnu/libgmp.a lytools lysieve lpthread lm ldl /usr/bin/ld: ./libysiqs.a(SIQS.o): in function `siqs_static_init': /home/bur/Math/yafu/factor/qs/SIQS.c:2309: undefined reference to `nextRoots_32k_avx2_intrin' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_open': savefile.c:(.text+0x142): undefined reference to `gzopen64' /usr/bin/ld: savefile.c:(.text+0x266): undefined reference to `gzopen64' /usr/bin/ld: savefile.c:(.text+0x2a1): undefined reference to `gzopen64' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_close': savefile.c:(.text+0x341): undefined reference to `gzclose' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_write_line': savefile.c:(.text+0x461): undefined reference to `gzputs' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_flush': savefile.c:(.text+0x4e4): undefined reference to `gzputs' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_eof': savefile.c:(.text+0x371): undefined reference to `gzeof' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_read_line': savefile.c:(.text+0x3f0): undefined reference to `gzgets' /usr/bin/ld: ../msieve//libmsieve.a(savefile.o): in function `savefile_rewind': savefile.c:(.text+0x521): undefined reference to `gzrewind' collect2: error: ld returned 1 exit status make: *** [Makefile:368: yafu] Error 1 
20220620, 17:11  #344 
"Jane Sullivan"
Jan 2011
Beckenham, UK
3^{2}·5·7 Posts 
I've got another of those "it won't factor it" jobbies in Yafu 2.08. For some reason it won't go into QS/SIQS.
Code:
06/20/22 16:15:39, 06/20/22 16:15:39, **************************** 06/20/22 16:15:39, Starting factorization of 7036874796802706717792076127030118075734377553821445738998743574873144601450291676951142421607390370359561 06/20/22 16:15:39, using pretesting plan: deep 06/20/22 16:15:39, using tune info for qs/gnfs crossover 06/20/22 16:15:39, **************************** 06/20/22 16:15:39, div: found prime factor = 137 06/20/22 16:15:39, div: found prime factor = 433 06/20/22 16:15:39, rho: x^2 + 3, starting 1000 iterations on C102 06/20/22 16:15:39, rho: x^2 + 2, starting 1000 iterations on C102 06/20/22 16:15:39, rho: x^2 + 1, starting 1000 iterations on C102 06/20/22 16:15:39, pm1: starting B1 = 150K, B2 = gmpecm default on C102 06/20/22 16:15:39, current ECM pretesting depth: 0.00 06/20/22 16:15:39, scheduled 30 curves at B1=2000 toward target pretesting depth of 34.00 06/20/22 16:15:39, ecm: commencing 32 curves using AVXECM method on 118623671158657249840563647393505134366149888805337835488254472697242875228844619560545884621085119441, B1=2k, B2=200k 06/20/22 16:15:39, ecm: finished 32 curves using AVXECM method on C102 input, B1=2k, B2=200k 06/20/22 16:15:39, current ECM pretesting depth: 15.19 06/20/22 16:15:39, scheduled 74 curves at B1=11000 toward target pretesting depth of 34.00 06/20/22 16:15:41, Finished 74 curves using GMPECM method on C102 input, B1=11k, B2=gmpecm default 06/20/22 16:15:41, current ECM pretesting depth: 20.24 06/20/22 16:15:41, scheduled 214 curves at B1=50000 toward target pretesting depth of 34.00 06/20/22 16:15:52, Finished 214 curves using GMPECM method on C102 input, B1=50k, B2=gmpecm default 06/20/22 16:15:52, pm1: starting B1 = 3750K, B2 = gmpecm default on C102 06/20/22 16:15:53, current ECM pretesting depth: 25.33 06/20/22 16:15:53, scheduled 430 curves at B1=250000 toward target pretesting depth of 34.00 06/20/22 16:17:25, Finished 430 curves using GMPECM method on C102 input, B1=250k, B2=gmpecm default 06/20/22 16:17:25, pm1: starting B1 = 15M, B2 = gmpecm default on C102 06/20/22 16:17:28, current ECM pretesting depth: 30.45 06/20/22 16:17:28, scheduled 643 curves at B1=1000000 toward target pretesting depth of 34.00 06/20/22 16:28:35, Finished 643 curves using GMPECM method on C102 input, B1=1M, B2=gmpecm default 06/20/22 16:28:35, final ECM pretested depth: 34.01 06/20/22 16:28:35, c102 cofactor = 118623671158657249840563647393505134366149888805337835488254472697242875228844619560545884621085119441 06/20/22 16:28:35, Total factoring time = 776.2737 seconds 
20220622, 07:37  #345 
Jun 2021
11110_{2} Posts 
The next stage for this number must to be GNFS

20220622, 07:43  #346 
"Curtis"
Feb 2005
Riverside, CA
3·1,831 Posts 
No, a C102 can easily be solved by QS. It's not the ideal method, but shouldn't be more than 23x slower than GNFS.

20220622, 08:30  #347 
"Jane Sullivan"
Jan 2011
Beckenham, UK
3^{2}×5×7 Posts 

20220709, 00:56  #348  
"James Heinrich"
May 2004
exNorthern Ontario
3,851 Posts 
Why does YAFU (observed in both 1.34 and 2.07) like to do a bit more ECM when you've told it that the target amount of ECM has already been done?
Quote:


20220712, 17:15  #349 
Jul 2022
3 Posts 
A bug in special form detection
Yafu (the executable from Github), when run on "101^101+2", first finds the special form, then claims it can't find it.
Code:
nfs: searching for brent special forms... nfs: input divides 101^101 + 2 nfs: searching for homogeneous cunningham special forms... nfs: searching for XYYXF special forms... nfs: searching for direct special forms... nfs: snfs form detection took 0.365021 seconds nfs: couldn't find special form 
20220712, 17:28  #350 
Jul 2022
3_{16} Posts 
crash with threads>1 on Fermat numbers
With threads=3, YAFU crashes on both 2^256+1 and 2^512+1 somewhere in ECM.
With threads=1, factorization of 2^256+1 succeeds. I have no patience to wait for 2^512+1, but probably OS: Windows 7, AVX2capable hardware, YAFU executable from Github. 
20220712, 20:12  #351  
"Jane Sullivan"
Jan 2011
Beckenham, UK
3^{2}·5·7 Posts 
Quote:
When yafu says Code:
scheduled 379 curves at B1=32765 toward target pretesting depth of 36.33 What happens if you tell yafu that input has been pretested to t36.34? Last fiddled with by BudgieJane on 20220712 at 20:13 Reason: typo 

20220713, 15:29  #352 
"Ben"
Feb 2007
2^{5}×5×23 Posts 
Yeah, it is a significant digits related issue, printed here with more precision enabled:
Code:
07/13/22 10:24:25, input indicated to have been pretested to t36.33 07/13/22 10:24:25, **************************** 07/13/22 10:24:25, current ECM pretesting depth: 36.330000000000 07/13/22 10:24:25, scheduled 379 curves at B1=0 toward target pretesting depth of 36.330000000000 07/13/22 10:24:25, rho: x^2 + 3, starting 1000 iterations on C109 07/13/22 10:24:25, rho: x^2 + 2, starting 1000 iterations on C109 07/13/22 10:24:25, rho: x^2 + 1, starting 1000 iterations on C109 07/13/22 10:24:25, current ECM pretesting depth: 36.331171089718 07/13/22 10:24:25, scheduled 382 curves at B1=3000000 toward target pretesting depth of 36.333333333333 Putting in work 36.34 causes it to skip ecm as now the threshold is exceeded. I hope that's acceptable as a work around? 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
yafu ignoring yafu.ini  chris2be8  YAFU  9  20220217 17:52 
Running YAFU via Aliqueit doesn't find yafu.ini  EdH  YAFU  8  20180314 17:22 
YAFU1.34  bsquared  YAFU  119  20151105 16:24 
Yafu bug.  storflyt32  YAFU  2  20150629 05:19 
yafu 1.32  bsquared  YAFU  28  20120720 16:17 