YAFU Version 2.10

bsquared · 2022-09-20, 13:49

I checked in version 2.10.

Hopefully fixes the recently reported crashing issue right after yafu starts on systems without BMI1/2 (this is still not something I can directly test, so let me know if the problem still exists).

Also fixes the problem where primitive/algebraic factor detection left a prime number that NFS tried to factor. Now if that happens the factorization should finish.

The new/improved microecm is also included (added to the makefile/build). Thanks again to Jeff Hurchalla.

Almost forgot... external GPU-ECM binaries are now supported, optionally with Seth Trosi's CGBN enhancements. new options: "gpucurves", "cgbn", "use_gpuecm", "use_gpudev". Note that if you are using GPU-ECM with "factor()", then you'll probably want to make use of the "ext_ecm" option. This option sets when to switch over from internal non-gpu ECM to the external GPU-ECM binary. Otherwise, for example, factor() will try to use potentially thousands of GPU curves at B1=50000 when it only needs a few hundred. If you have AVX-ECM, then that will still be used as the internal ECM version before switching to external GPU-ECM.

Finally, I fixed several memory leaks after updating to a new version of valgrind. Either valgrind doesn't know how to deal with avx512 instructions or I don't know how to use it correctly, so the memory leaks were investigated without any of that code path... possibly some still exist there. But overall the situation should be improved.

If you are building from source you will also need to get the newest version of ytools/ysieve. Some of the memory leaks and fixes were in the ysieve library.

kruoli · 2022-09-20, 15:26

Does it require a self-compiled binary for the fix for Ivy Bridge etc.? The .exe in your GIT repository still crashed on startup on Ivy Bridge, Windows 7.

James Heinrich · 2022-09-20, 15:29

Quote:

Originally Posted by kruoli

Does it require a self-compiled binary for the fix for Ivy Bridge etc.?
The .exe in your GIT repository still crashed on startup on Ivy Bridge, Windows 7.

It was my understanding that none of the v2.0 YAFU will ever work on Windows 7. Crashing on old CPUs under Win10 I think was a different issue.

For what it's worth v2.10 seems to run fine on my i3-8100/Win10.

bsquared · 2022-09-20, 15:35

Quote:

Originally Posted by James Heinrich

It was my understanding that none of the v2.0 YAFU will ever work on Windows 7. Crashing on old CPUs under Win10 I think was a different issue.

For what it's worth v2.10 seems to run fine on my i3-8100/Win10.

I don't know why it would crash on windows 7 and not windows 10. But my understanding of the dependencies of Visual Studio 2022 is very murky. Maybe it requires win10....

My hope is that it is a cpu-feature problem, not a windows version problem. But I can't directly test either one.

I highly recommend WSL/ubuntu if you're running windows. IIRC that is available for windows 7?

It looks like Ivy Bridge doesn't have either AVX2 or BMI2. But this *should* be detected and those features not used by either ysieve or yafu. Can you start up with -v -v -v -v and see if anything extra is printed?

James Heinrich · 2022-09-20, 15:54

Quote:

Originally Posted by bsquared

I don't know why it would crash on windows 7 and not windows 10.
My hope is that it is a cpu-feature problem, not a windows version problem. But I can't directly test either one.

I'm happy to do any testing you want on my i7-3930K (Sandy Bridge).

Quote:

Originally Posted by bsquared

I highly recommend WSL/ubuntu if you're running windows. IIRC that is available for windows 7?

No. If it's the WSL I think you mean, WSL is a compatibility layer for running Linux binary executables (in ELF format) natively on Windows 10, Windows 11, and Windows Server 2019.

Quote:

Originally Posted by bsquared

It looks like Ivy Bridge doesn't have either AVX2 or BMI2. But this *should* be detected and those features not used by either ysieve or yafu. Can you start up with -v -v -v -v and see if anything extra is printed?

Quadverbosity makes no difference that I notice. See attached. Crash details:

Code:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	yafu-x64.exe
  Application Version:	0.0.0.0
  Application Timestamp:	6329c003
  Fault Module Name:	yafu-x64.exe
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	6329c003
  Exception Code:	c000001d
  Exception Offset:	0000000000001300
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	e63c
  Additional Information 2:	e63cb477893153aa77789ca6de3c6a1b
  Additional Information 3:	2fdb
  Additional Information 4:	2fdb2bf6e03bebbe6df1b584e671261b

kruoli · 2022-09-20, 15:57

As far as I know, WSL is not availible for Windows 7.

Requested test:

Code:

C:\tmp>yafu -v -v -v -v
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) Core(TM) i7-3630QM CPU @ 2.40GHz
Detected L1 = 32768 bytes, L2 = 6291456 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 C:\tmp

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

>>

...and then crashed as usual.
Error at 0x000000013F641300 in yafu.exe: 0xC000001D: Illegal Instruction

bsquared · 2022-09-20, 16:17

Can you share the last 10-15 lines of session.log after an attempted startup?

storm5510 · 2022-09-20, 17:19

Quote:

Originally Posted by bsquared

It should work on systems without AVX2, but I don't have any of those to test on anymore, so apparently it doesn't. Based on where it crashes it would seem the problem lies in the ysieve library, since one of the first things yafu does is create and store a small list of primes.

Link please. I can't test it if I can't find it...

bsquared · 2022-09-20, 17:25

Quote:

Originally Posted by storm5510

Link please. I can't test it if I can't find it...

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.

James Heinrich · 2022-09-20, 18:03

Quote:

Originally Posted by bsquared

Can you share the last 10-15 lines of session.log after an attempted startup?

Empty. If I delete session.log it gets created as a zero-byte file but nothing is written to it before the crash (or after for that matter).

storm5510 · 2022-09-20, 23:30

Quote:

Originally Posted by bsquared

Here.

Thank you for the reply. The link appears to be to a Linux build. I read some install instructions EdH wrote and it sailed over my head. I have been running a Windows build, v2.09. It does fine. My Ubuntu box is usually busy with CADO-NFS.

2022-09-20, 13:49	#1
bsquared "Ben" Feb 2007 2²·941 Posts	YAFU Version 2.10 I checked in version 2.10. Hopefully fixes the recently reported crashing issue right after yafu starts on systems without BMI1/2 (this is still not something I can directly test, so let me know if the problem still exists). Also fixes the problem where primitive/algebraic factor detection left a prime number that NFS tried to factor. Now if that happens the factorization should finish. The new/improved microecm is also included (added to the makefile/build). Thanks again to Jeff Hurchalla. Almost forgot... external GPU-ECM binaries are now supported, optionally with Seth Trosi's CGBN enhancements. new options: "gpucurves", "cgbn", "use_gpuecm", "use_gpudev". Note that if you are using GPU-ECM with "factor()", then you'll probably want to make use of the "ext_ecm" option. This option sets when to switch over from internal non-gpu ECM to the external GPU-ECM binary. Otherwise, for example, factor() will try to use potentially thousands of GPU curves at B1=50000 when it only needs a few hundred. If you have AVX-ECM, then that will still be used as the internal ECM version before switching to external GPU-ECM. Finally, I fixed several memory leaks after updating to a new version of valgrind. Either valgrind doesn't know how to deal with avx512 instructions or I don't know how to use it correctly, so the memory leaks were investigated without any of that code path... possibly some still exist there. But overall the situation should be improved. If you are building from source you will also need to get the newest version of ytools/ysieve. Some of the memory leaks and fixes were in the ysieve library. Last fiddled with by bsquared on 2022-09-20 at 13:58 Reason: Almost forgot about gpu-ecm options.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How I install YAFU version 2 onto my Ubuntu Machines	EdH	EdH	7	2023-03-14 15:06
yafu ignoring yafu.ini	chris2be8	YAFU	9	2022-02-17 17:52
YAFU Version Differences	nivek000	YAFU	2	2021-12-21 16:21
Running YAFU via Aliqueit doesn't find yafu.ini	EdH	YAFU	8	2018-03-14 17:22
YAFU version 1.31	bsquared	YAFU	26	2012-04-23 03:16

2022-09-20, 15:26	#2
kruoli "Oliver" Sep 2017 Porta Westfalica, DE 1,559 Posts	Does it require a self-compiled binary for the fix for Ivy Bridge etc.? The .exe in your GIT repository still crashed on startup on Ivy Bridge, Windows 7.

2022-09-20, 16:17	#7
bsquared "Ben" Feb 2007 EB4₁₆ Posts	Can you share the last 10-15 lines of session.log after an attempted startup?