YAFU Version 2.10

[James Heinrich]

Originally Posted by storm5510

The link appears to be to a Linux build

No, it's the Windows build. Note however that it's a link to a webpage from which you can download it, do not save-link-as directly -- open the link in your browser then click the Download button.
Or download it from https://download.mersenne.ca/YAFU if you prefer.

[storm5510]

Originally Posted by James Heinrich

No, it's the Windows build. Note however that it's a link to a webpage from which you can download it, do not save-link-as directly -- open the link in your browser then click the Download button.
Or download it from https://download.mersenne.ca/YAFU if you prefer.

Thank you. Most kind.

[bsquared]

Originally Posted by bsquared

Here.

By the way, I now suspect the linked GMP library as the problem, since the initial batch of primes is found just fine. The illegal instruction could lie in GMP's random number generator setup.

I checked in yafu-x64-gc.exe, which I created by linking against a generic C version of MPIR-3.0.0. Please test it and see if it's any better.

[James Heinrich]

Originally Posted by bsquared

I checked in yafu-x64-gc.exe, which I created by linking against a generic C version of MPIR-3.0.0. Please test it and see if it's any better.

It's no better for me. Same crash (after startup) and session.log is still empty.

[WraithX]

Btw, just like last time (post 175 in this thread) I am able to run yafu 2.10 on my Windows 7 x64 computer without any problems.

D:\yafu\yafu_2.10>yafu-x64.exe
warning: could not open yafu.ini, no options parsed


YAFU Version 2.10
Built with Microsoft Visual Studio 1931
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz
Detected L1 = 32768 bytes, L2 = 31457280 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 D:\yafu\yafu_2.10

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> aprcl(2^31-1)

P =  5, Q =           11  (88.89%)
Input is prime.  P10

ans = 2147483647

>> factor(10^19+49)

fac: factoring 10000000000000000049
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 C20
Total factoring time = 0.0312 seconds


***factors found***

P10 = 8532383917
P10 = 1172005397

ans = 1

[James Heinrich]

Originally Posted by WraithX

Btw, just like last time (post 175 in this thread) I am able to run yafu 2.10 on my Windows 7 x64 computer without any problems.

Interesting.

Per your other post I installed Microsoft Visual C++ 2015-2022 Redistributable (x64) 14.32.31332 both x64 and x86 versions but made no difference, same crash.
I don't see much hardware feature difference between your Xeon E5-2687W and my i7-3930K.

[WraithX]

I'm not sure if the windbg (windows debugger) can help track down what the illegal instruction is, but it may be worth a shot. You can install it by downloading the Windows SDK for Win 10

Windows SDK - With WinDbg

Download the Windows SDK (it will say for Windows 10, but the installation page says it supports Windows 7 SP1). Then, to just get the debugger, the instructions say:

In the SDK installation wizard, select Debugging Tools for Windows, and deselect all other components.

At this point it would take more googling to find out how to use the debugger to start the program, run it until the problem occurs, and then find out what instruction is causing the crash. I hope this can help you track down this problem!

[James Heinrich]

Originally Posted by WraithX

Download the Windows SDK (it will say for Windows 10, but the installation page says it supports Windows 7 SP1)

I got it installed, but can't seem to start it, api-ms-win-core-com-l1-1-0.dll is missing (not sure if that might be a Win10 thing?).

[bsquared]

I re-uploaded yafu-x64-gc.exe.

This time I did a complete rebuild of the entire dependency chain starting with mpir-3.0.0 (core2), then ecm-7.0.4, ytools, ysieve, and yafu. In all MSVC projects I set the "enable enhanced instruction set" option in the code generation settings tab to "No Enhanced Instructions (/arch/IA32)". Although I don't know if this does anything because I see the message:
"1>cl : command line warning D9002: ignoring unknown option '/arch:IA32'"
scroll by when compiling. weird.

Thanks for testing!

[James Heinrich]

Originally Posted by bsquared

I re-uploaded yafu-x64-gc.exe

C:\Users\User\Desktop\yafu>yafu-2.10-202209211825-win64-gc.exe

YAFU Version 2.10
Built with Microsoft Visual Studio 1931
Using GMP-ECM 7.0.4, Powered by MPIR 3.0.0
Detected        Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Detected L1 = 32768 bytes, L2 = 12582912 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991
Parsed yafu.ini from C:\Users\User\Desktop\yafu

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(1460028439856908668755525958205639140519011347819950733167960266924037979)
...
Lanczos elapsed time = 1.0690 seconds.
Sqrt elapsed time = 0.0060 seconds.
SIQS elapsed time = 107.7832 seconds.
pretesting / qs ratio was 0.08
Total factoring time = 116.5047 seconds
***factors found***
P36 = 348746364767500102806150303982379243
P37 = 4186505114770932960236858078590076753
ans = 1

However, while running tune() it crashed (attached) on the second test (according to factor.log):

09/21/22 18:56:12, starting SIQS on c60: 349594255864176572614071853194924838158088864370890996447417
09/21/22 18:56:12, random seed: 8752402939882152805
09/21/22 18:56:12, ==== sieve params ====
09/21/22 18:56:12, n = 62 digits, 205 bits
09/21/22 18:56:12, factor base: 3504 primes (max prime = 71333)
09/21/22 18:56:12, single large prime cutoff: 4993310 (70 * pmax)
09/21/22 18:56:12, allocating 2 large prime slices of factor base
09/21/22 18:56:12, buckets hold 2048 elements
09/21/22 18:56:12, large prime hashtables have 65536 bytes
09/21/22 18:56:12, using SSE41 enabled 32k sieve core
09/21/22 18:56:12, sieve interval: 2 blocks of size 32768
09/21/22 18:56:12, polynomial A has ~ 7 factors
09/21/22 18:56:12, using multiplier of 145
09/21/22 18:56:12, using multiplier of 145
09/21/22 18:56:12, using Q2(x) polynomials for kN mod 8 = 1
09/21/22 18:56:12, using SPV correction of 15 bits, starting at offset 34
09/21/22 18:56:12, trial factoring cutoff at 68 bits
09/21/22 18:56:12, ==== sieving started (1 thread) ====
09/21/22 18:56:14, trial division touched 105151 sieve locations out of 1519386624
09/21/22 18:56:14, total reports = 105151, total surviving reports = 61230
09/21/22 18:56:14, total blocks sieved = 46368, avg surviving reports per block = 1.32
09/21/22 18:56:14, 1772 relations found: 1050 full + 722 from 9948 partial, using 11592 polys (183 A polys)
09/21/22 18:56:14, on average, sieving found 0.95 rels/poly and 5668.75 rels/sec
09/21/22 18:56:14, trial division touched 105151 sieve locations out of 1519386624
09/21/22 18:56:14, ==== post processing stage (msieve-1.38) ====
09/21/22 18:56:14, starting SIQS on c65: 34053408309992030649212497354061832056920539397279047809781589871
09/21/22 18:56:14, random seed: 17728683799165162768
09/21/22 18:56:14, ==== sieve params ====
09/21/22 18:56:14, n = 67 digits, 220 bits
09/21/22 18:56:14, factor base: 6384 primes (max prime = 136207)
09/21/22 18:56:14, single large prime cutoff: 10215525 (75 * pmax)
09/21/22 18:56:14, allocating 3 large prime slices of factor base
09/21/22 18:56:14, buckets hold 2048 elements
09/21/22 18:56:14, large prime hashtables have 98304 bytes
09/21/22 18:56:14, using SSE41 enabled 32k sieve core
09/21/22 18:56:14, sieve interval: 2 blocks of size 32768
09/21/22 18:56:14, polynomial A has ~ 8 factors
09/21/22 18:56:14, using multiplier of 47
09/21/22 18:56:14, using multiplier of 47
09/21/22 18:56:14, using Q2(x) polynomials for kN mod 8 = 1
09/21/22 18:56:14, using SPV correction of 20 bits, starting at offset 40
09/21/22 18:56:14, trial factoring cutoff at 74 bits
09/21/22 18:56:14, ==== sieving started (1 thread) ====
09/21/22 18:56:24, trial division touched 383544 sieve locations out of 5371330560
09/21/22 18:56:24, total reports = 383544, total surviving reports = 127599
09/21/22 18:56:24, total blocks sieved = 163920, avg surviving reports per block = 0.78
09/21/22 18:56:24, 1274 relations found: 756 full + 518 from 10324 partial, using 40980 polys (619 A polys)
09/21/22 18:56:24, on average, sieving found 0.27 rels/poly and 1104.51 rels/sec
09/21/22 18:56:24, trial division touched 383544 sieve locations out of 5371330560
09/21/22 18:56:24, ==== post processing stage (msieve-1.38) ====

[bsquared]

Sweet! Good to see progress.

Actually I realized now that I didn't update the msieve dependency, so maybe that will take care of the error you're seeing now. Might not be able to get that updated until tomorrow.