[QUOTE=Citrix;546825]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.[/QUOTE]

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.

[QUOTE=rogue;546828]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.[/QUOTE]

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.

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.

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

[QUOTE=rogue;546942]I posted 2.0.1. This fixes gcwsieve and adds k1b2sieve which sieves 2*n+c for a range of n and c.[/QUOTE]
Link?

[QUOTE=pepi37;546997]Link?[/QUOTE]

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

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.

[QUOTE=pepi37;547038]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.[/QUOTE]

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

[QUOTE=rogue;547040]How large a range are you sieving? Is this on Windows? How many threads are you running with?[/QUOTE]


I run it on hexacore CPU ,Win10

range was from 113853849125 to 213853849125 base 2

[QUOTE=pepi37;547042]I run it on hexacore CPU ,Win10

range was from 113853849125 to 213853849125 base 2[/QUOTE]

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.

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