Compiling YAFU for Windows using mingw

[bsquared]

Also, here is r388 with AVX512 enabled code. I've folded my AVX-ECM implementation into this latest version, which is 1.5x to 2.5x higher throughput than gmp-ecm (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.

[Madpoo]

Originally Posted by bsquared

First off, sorry for all of the difficulty here. I have not been in the habit of checking for successful builds on windows when checking in code, especially for older systems. It is also no fun that mingw builds take *so long*.

I've attached a build of the most recent version with only SSE4.1 activated in yafu. The underlying gmp and ecm builds I believe used -march=k8 and msieve had no special -march
<....>
With those caveats, hopefully this works.

I got this:
"The program can't start because msys-2.0.dll is missing..."

It must be something that mingw uses? Not familiar with it.

[James Heinrich]

Originally Posted by Madpoo

"The program can't start because msys-2.0.dll is missing..."

I put a copy of the version I have in the YAFU mirror.

[sodiseng]

Originally Posted by bsquared

Also, here is r388 with AVX512 enabled code. I've folded my AVX-ECM implementation into this latest version, which is 1.5x to 2.5x higher throughput than gmp-ecm (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.

yea,its faster.
but it has a issue.
u need add ".exe" when start ggnfs.
im sure the .ini is correct

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

[sodiseng]

Originally Posted by bsquared

Also, here is r388 with AVX512 enabled code. I've folded my AVX-ECM implementation into this latest version, which is 1.5x to 2.5x higher throughput than gmp-ecm (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.

its need add ".exe" when start gnfs
there is error msg

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

im sure the path is correct in .ini file

[chris2be8]

Originally Posted by sodiseng

nfs: could not open output file, possibly bad path to siever

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.

[kruoli]

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?).

[silvio]

Hi all! Noobie here so please bear with me. I can't compile msieve. this is what i get:
cannot find -ldl: No such file or directory
collect2.exe: error: ld returned 1 exit status
make: *** [Makefile:279: all] Error 1
Could anybody explain how to do? Best regards

[swellman]

Have you tried EdH’s set of excellent instructions? It’s for Linux, specifically Ubuntu but it might help you.

https://www.mersenneforum.org/showthread.php?t=23085

[silvio]

Originally Posted by swellman

Have you tried EdH’s set of excellent instructions? It’s for Linux, specifically Ubuntu but it might help you.

https://www.mersenneforum.org/showthread.php?t=23085

Hi! thanks for immediate answer. Yes i did. But for the life of me I can't build yafu that way.
What is the missing file ld?
TIA

[silvio]

oh my! I just want to build yafu in Windows