CADO-NFS on windows
 

It does install with cygwin, win 8.1. I wish I could just use binaries though.
For anyone else trying to compile, here are the fixes to the problems I ran into:

CMake will not download: install through cygwin. The option for downloading on-the-fly should be disabled for windows builds because it does not work.
child_info_fork::abort: [...] Loaded to different address: ... [URL="http://cygwin.wikia.com/wiki/Rebaseall"]Rebaseall[/URL] with dash.exe as administrator
The C compiler identification is unknown, The CXX compiler identification is unknown, cc.exe failed: run through cygwin terminal and not cmd

Also I had to install at least 20 new packages in cygwin with setup-x86.exe. I already had gcc, g++, python 2 and 3 installed, but they have to be reinstalled. It is currently in an install loop.

For now it is stuck on repeating the following:
[CODE]cd /cygdrive/c/cado-nfs-2.2.0/gf2x && C:/cygwin/bin/sh.exe /cygdrive/c/cado-nfs-2.2.0/gf2x/config/missing automake-1.15 --gnu Makefile
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.15 line 3936.
running CONFIG_SHELL=/bin/sh /bin/sh /cygdrive/c/cado-nfs-2.2.0/gf2x/configure --disable-shared --disable-dependency-tracking --enable-fft-interface CC=/usr/bin/cc CXX=/usr/bin/c++.exe CFLAGS=-std=c99 -g -W -Wall -O2 -I/usr/local/include -I/cygdrive/c/cado-nfs-2.2.0 CXXFLAGS=-std=c++11 -g -W -Wall -Wno-literal-suffix -O2 -I/usr/local/include -I/cygdrive/c/cado-nfs-2.2.0 LDFLAGS=-Wl,-rpath,/usr/local/lib -L/usr/local/lib --disable-sse2 --no-create --no-recursion
checking build system type... pentium3-pc-cygwin
checking host system type... pentium3-pc-cygwin
checking target system type... pentium3-pc-cygwin
checking for gcc... /usr/bin/cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/cc accepts -g... yes
checking for /usr/bin/cc option to accept ISO C89... none needed
checking whether /usr/bin/cc understands -c and -o together... yes
checking how to run the C preprocessor... /usr/bin/cc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of /usr/bin/cc... none
checking whether to enable maintainer-specific portions of Makefiles... no
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by /usr/bin/cc... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 8192
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert pentium3-pc-cygwin file names to pentium3-pc-cygwin format... func_convert_file_noop
checking how to convert pentium3-pc-cygwin file names to toolchain format... func_convert_file_noop
checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL
checking for dlltool... dlltool
checking how to associate runtime and link libraries... func_cygming_dll_for_implib
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from /usr/bin/cc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if /usr/bin/cc supports -fno-rtti -fno-exceptions... /cygdrive/c/cado-nfs-2.2.0/gf2x/configure: line 8406: diff: command not found
no
checking for /usr/bin/cc option to produce PIC... -DDLL_EXPORT -DPIC
checking if /usr/bin/cc PIC flag -DDLL_EXPORT -DPIC works... yes
checking if /usr/bin/cc static flag -static works... yes
checking if /usr/bin/cc supports -c -o file.o... yes
checking if /usr/bin/cc supports -c -o file.o... (cached) yes
checking whether the /usr/bin/cc linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for gcc... (cached) /usr/bin/cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/cc accepts -g... (cached) yes
checking for /usr/bin/cc option to accept ISO C89... (cached) none needed
checking whether /usr/bin/cc understands -c and -o together... (cached) yes
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/c++.exe accepts -g... yes
checking dependency style of /usr/bin/c++.exe... none
checking how to run the C++ preprocessor... /usr/bin/c++.exe -E
checking for ld used by /usr/bin/c++.exe... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking whether the /usr/bin/c++.exe linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
checking for /usr/bin/c++.exe option to produce PIC... -DDLL_EXPORT -DPIC
checking if /usr/bin/c++.exe PIC flag -DDLL_EXPORT -DPIC works... yes
checking if /usr/bin/c++.exe static flag -static works... yes
checking if /usr/bin/c++.exe supports -c -o file.o... yes
checking if /usr/bin/c++.exe supports -c -o file.o... (cached) yes
checking whether the /usr/bin/c++.exe linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking warning verbosity option... -Wall -W for C++ -Wall -W for C
checking for /usr/bin/cc option to accept ISO C99... none needed
checking build system compiler /usr/bin/cc... yes
checking for build system executable suffix... .exe
checking for GMP or MPIR... yes
checking for recent GMP or MPIR... yes
checking size of unsigned long... 4
checking whether /usr/bin/cc can compile and run sse-2 code... explicitly disabled, no
checking whether /usr/bin/cc can compile and run sse-3 code... skipped, no
checking whether /usr/bin/cc can compile and run ssse3 code... skipped, no
checking whether /usr/bin/cc can compile and run sse-4.1 code... skipped, no
checking whether /usr/bin/cc can compile pclmulqdq and if it is supported by the hardware... skipped, no
configure: using ABI="default"
configure: CC="/usr/bin/cc"
configure: CFLAGS="-std=c99 -g -W -Wall -O2 -I/usr/local/include -I/cygdrive/c/cado-nfs-2.2.0 -Wall -W"
configure: CPPFLAGS=""
configure: hwdir="generic32"
checking the number of bits in an unsigned long... 32
checking whether already_tuned/generic32/ is right assuming 32-bits unsigned longs... yes
File /cygdrive/c/cado-nfs-2.2.0/gf2x/toom-gpl.c is a placeholder, using an LGPL-licensed gf2x
checking that generated files are newer than configure... done
configure: creating ./config.status
C:/cygwin/bin/sh.exe ./config.status
config.status: creating version.sh
config.status: creating Makefile
config.status: creating tests/Makefile
config.status: creating lowlevel/Makefile
config.status: creating src/Makefile
config.status: creating fft/Makefile
config.status: creating apps/Makefile
config.status: creating gf2x/gf2x-config.h
config.status: creating gf2x/gf2x-config-export.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic32/gf2x-thresholds.h to gf2x/gf2x-thresholds.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic32/gf2x_mul1.h to gf2x/gf2x_mul1.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul2.h to gf2x/gf2x_mul2.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul3.h to gf2x/gf2x_mul3.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul4.h to gf2x/gf2x_mul4.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul5.h to gf2x/gf2x_mul5.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul6.h to gf2x/gf2x_mul6.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul7.h to gf2x/gf2x_mul7.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul8.h to gf2x/gf2x_mul8.h
config.status: linking /cygdrive/c/cado-nfs-2.2.0/gf2x/already_tuned/generic/gf2x_mul9.h to gf2x/gf2x_mul9.h
config.status: executing depfiles commands
config.status: executing libtool commands
[/CODE]

Does anyone have pre-compiled binaries for x86-64?

I think building a linux VM to run CADO is the easier alternative. I had success with that path, and the VM doesn't cost any meaningful speed.

If performance is comparable to YAFU, I think I'll just be sticking with that.

There's no reason to think CADO is any faster than ggnfs (the siever used by YAFU). CADO's big advantage is the simple way a job can be distributed over multiple machines.

[QUOTE=VBCurtis;420648]There's no reason to think CADO is any faster than ggnfs (the siever used by YAFU). CADO's big advantage is the simple way a job can be distributed over multiple machines.[/QUOTE]There's a reason to suggest that it is slower. That has been my experience throughout.

Perhaps some of us should address that deficiency in our copious free time.

I did a comparison for small numbers. I would be nice to extend up to 512 bits or so.

[url]http://www.mersenneforum.org/showthread.php?t=15109[/url]

[QUOTE=bsquared;420682]I did a comparison for small numbers. I would be nice to extend up to 512 bits or so.

[url]http://www.mersenneforum.org/showthread.php?t=15109[/url][/QUOTE]

And repeat with a newer faster version of cado.

On my computer, YAFU insists on using the quadratic sieve for a 110 digit number. Or maybe I configured it wrong?

I agree with henryzz. CADO lists significant speed increases (2x faster) on their website from version 1.1 to 2.1.

[QUOTE=jux;420722]On my computer, YAFU insists on using the quadratic sieve for a 110 digit number. Or maybe I configured it wrong?[/QUOTE]
It may be normal, depending on the CPU. I had that case on a computer with an i7-2600. Did you run "-tune" command? If not, please do! Usually the crossover is under 105 digits. Running the "-tune" can make the things faster around that point. If the nfs sieving is slow, due to whatever reasons, memory, etc., then the QS became comparatively faster and the crossover point is pushed higher.

You may need to delete the old tuning info from the ini file, before running the new tune.

Also, yafu may revert to SIQS if something wrong with external GNFS files (did you add the correct path to ggnfs executables in yafu.ini?) etc. or if a small factor pops up (which decreases the remaining composite length)