20200609, 14:16  #56 
"Ben"
Feb 2007
2·1,789 Posts 
Also, here is r388 with AVX512 enabled code. I've folded my AVXECM implementation into this latest version, which is 1.5x to 2.5x higher throughput than gmpecm (so ecm_ext can be set to something like 11000000 again). And SIQS is about 25% faster than the SSE41 version for larger inputs.
Having the same problems with system() calls with this mingw build though, so unfortunately NFS won't work. Let me know if other problems emerge. 
20200613, 17:41  #57  
Serpentine Vermin Jar
Jul 2014
3,313 Posts 
Quote:
"The program can't start because msys2.0.dll is missing..." It must be something that mingw uses? Not familiar with it. 

20200613, 18:06  #58 
"James Heinrich"
May 2004
exNorthern Ontario
2×1,753 Posts 
I put a copy of the version I have in the YAFU mirror.

20200821, 16:27  #59  
Aug 2020
2 Posts 
Quote:
but it has a issue. u need add ".exe" when start ggnfs. im sure the .ini is correct Code:
nfs: continuing with sieving  could not determine last special q; using default startq nfs: commencing algebraic side lattice sieving over range: 16150000  16160000 nfs: commencing algebraic side lattice sieving over range: 16000000  16010000 nfs: commencing algebraic side lattice sieving over range: 16030000  16040000 nfs: commencing algebraic side lattice sieving over range: 16040000  16050000 nfs: commencing algebraic side lattice sieving over range: 16010000  16020000 nfs: commencing algebraic side lattice sieving over range: 16070000  16080000 nfs: commencing algebraic side lattice sieving over range: 16020000  16030000 nfs: commencing algebraic side lattice sieving over range: 16080000  16090000 nfs: commencing algebraic side lattice sieving over range: 16100000  16110000 nfs: commencing algebraic side lattice sieving over range: 16140000  16150000 nfs: commencing algebraic side lattice sieving over range: 16110000  16120000 nfs: commencing algebraic side lattice sieving over range: 16130000  16140000 nfs: commencing algebraic side lattice sieving over range: 16120000  16130000 nfs: commencing algebraic side lattice sieving over range: 16090000  16100000 nfs: commencing algebraic side lattice sieving over range: 16060000  16070000 nfs: commencing algebraic side lattice sieving over range: 16050000  16060000 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 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 

20200821, 16:31  #60  
Aug 2020
2_{16} Posts 
Quote:
there is error msg Code:
nfs: continuing with sieving  could not determine last special q; using default startq nfs: commencing algebraic side lattice sieving over range: 16150000  16160000 nfs: commencing algebraic side lattice sieving over range: 16000000  16010000 nfs: commencing algebraic side lattice sieving over range: 16030000  16040000 nfs: commencing algebraic side lattice sieving over range: 16040000  16050000 nfs: commencing algebraic side lattice sieving over range: 16010000  16020000 nfs: commencing algebraic side lattice sieving over range: 16070000  16080000 nfs: commencing algebraic side lattice sieving over range: 16020000  16030000 nfs: commencing algebraic side lattice sieving over range: 16080000  16090000 nfs: commencing algebraic side lattice sieving over range: 16100000  16110000 nfs: commencing algebraic side lattice sieving over range: 16140000  16150000 nfs: commencing algebraic side lattice sieving over range: 16110000  16120000 nfs: commencing algebraic side lattice sieving over range: 16130000  16140000 nfs: commencing algebraic side lattice sieving over range: 16120000  16130000 nfs: commencing algebraic side lattice sieving over range: 16090000  16100000 nfs: commencing algebraic side lattice sieving over range: 16060000  16070000 nfs: commencing algebraic side lattice sieving over range: 16050000  16060000 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 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 

20210922, 15:31  #61 
Sep 2009
2,179 Posts 
It's making a classic error by *not* saying what path it is looking for. It saves time in the long run to make sure error messages have all the information you are likely to need to work out what is wrong. I've been the one writing programs for other people to use, and taking care to make the messages informative.
This was well known long before Linux existed. 
20210923, 08:56  #62 
"Oliver"
Sep 2017
Porta Westfalica, DE
1010101000_{2} Posts 
You can try to diagnose with SysInternals ProcMon which path he is trying to open. After that, you maybe can change the ini file entry accordingly (missing/extra slash/backslash?).

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Guide to compiling YAFU  Mr. Odd  YAFU  4  20170424 15:40 
Compiling YAFU under MinGW  wombatman  YAFU  10  20160121 19:48 
Need help compiling YAFU from SVN.  Stargate38  YAFU  14  20160120 21:46 
compiling svn 427 for Windows 64 bit.  skan  NFSNET Discussion  7  20120418 10:30 
Compiling ECM 5.0.3 for windows  BotXXX  Factoring  25  20050913 12:24 