mtsieve - Page 31

rogue · 2020-05-30, 19:50

Quote:

Originally Posted by Citrix

You need to add gcwsievecl to

GPU_PROGS=afsievecl mfsievecl gfndsievecl pixsievecl xyyxsievecl

Compiles for me and at least I get
"gcwsievecl.exe -p 3770000000000 -P 4000000000000 -b 2 -n 825 -N 1000 -s +
gcwsieve v1.2, a program to find factors numbers of the form n*b^n+1 and n*b^n-1
Sieve started: 377e10 < p < 4e12 with 0 terms (825 <= n <= 1000, n*2^n+1) (expecting 0 factors)"

Then it crashes.

Hmm. Doesn't crash for me. Did you do a "make clean" before "make gcwsievecl"?

But I think I introduced another bug somewhere else as it was hanging on me.

Citrix · 2020-05-30, 20:07

Quote:

Originally Posted by rogue

Hmm. Doesn't crash for me. Did you do a "make clean" before "make gcwsievecl"?

But I think I introduced another bug somewhere else as it was hanging on me.

Clean build. No luck. still crashes.
It does not work with the original cw_kernel.cl file either.
I am on Windows 10 if that makes a difference.

rogue · 2020-05-30, 20:13

I found and fixed two issues in the CullenWoodallWorker class. It no longer hangs and it runs cleanly on OS X. One was caused by a change in the framework. The other by indexing beyond the bounds of an array. That latter triggers a crash on OS X, but behaves unpredictably on Windows.

rogue · 2020-06-01, 16:10

I posted 2.0.1. This fixes gcwsieve and adds k1b2sieve which sieves 2*n+c for a range of n and c.

pepi37 · 2020-06-02, 08:12

Quote:

Originally Posted by rogue

I posted 2.0.1. This fixes gcwsieve and adds k1b2sieve which sieves 2*n+c for a range of n and c.

Link?

rogue · 2020-06-02, 12:49

Quote:

Originally Posted by pepi37

Link?

https://sourceforge.net/projects/mtsieve/, but there are bugs in that sieve that I have to fix. I will hopefully post an update later today.

pepi37 · 2020-06-02, 19:57

One suggestion :using twinsieve on big range can easy consume 4, 8 or more GB of RAM: so I suggest that you add quick calculation at start that will show user how many RAM twinsieve will allocate.If user agree with prediction: then calculation is continuing.
I ran few times twinsieve and got out of memory. Newpgen solve this program as suggested above.

rogue · 2020-06-02, 20:47

Quote:

Originally Posted by pepi37

One suggestion :using twinsieve on big range can easy consume 4, 8 or more GB of RAM: so I suggest that you add quick calculation at start that will show user how many RAM twinsieve will allocate.If user agree with prediction: then calculation is continuing.
I ran few times twinsieve and got out of memory. Newpgen solve this program as suggested above.

How large a range are you sieving? Is this on Windows? How many threads are you running with?

pepi37 · 2020-06-02, 21:08

Quote:

Originally Posted by rogue

How large a range are you sieving? Is this on Windows? How many threads are you running with?

I run it on hexacore CPU ,Win10

range was from 113853849125 to 213853849125 base 2

rogue · 2020-06-02, 22:06

Quote:

Originally Posted by pepi37

I run it on hexacore CPU ,Win10

range was from 113853849125 to 213853849125 base 2

It takes up that much memory because you have 2e11 terms.

NewPGen only warns you because it is a 32-bit app and is limited on how much memory it can use. I don't see a reason for such a message in any of my sieves. They are all 64-bit so it is really an issue of how much memory you have available as opposed to how much memory the software can use.

pepi37 · 2020-06-02, 22:16

But reason is to warn user, twinsieve will use 12GB of ram and you have 8....(example)

2020-06-02, 22:16	#341
pepi37 Dec 2011 After milion nines:) 2⁷·11 Posts	But reason is to warn user, twinsieve will use 12GB of ram and you have 8....(example) Last fiddled with by pepi37 on 2020-06-02 at 22:16

2020-05-30, 20:13	#333
rogue "Mark" Apr 2003 Between here and the 2³·11·71 Posts	I found and fixed two issues in the CullenWoodallWorker class. It no longer hangs and it runs cleanly on OS X. One was caused by a change in the framework. The other by indexing beyond the bounds of an array. That latter triggers a crash on OS X, but behaves unpredictably on Windows.

2020-06-01, 16:10	#334
rogue "Mark" Apr 2003 Between here and the 14150₈ Posts	I posted 2.0.1. This fixes gcwsieve and adds k1b2sieve which sieves 2*n+c for a range of n and c.

2020-06-02, 19:57	#337
pepi37 Dec 2011 After milion nines:) 2600₈ Posts	One suggestion :using twinsieve on big range can easy consume 4, 8 or more GB of RAM: so I suggest that you add quick calculation at start that will show user how many RAM twinsieve will allocate.If user agree with prediction: then calculation is continuing. I ran few times twinsieve and got out of memory. Newpgen solve this program as suggested above.