Steve Searle has recently modified the lasieve v5 assembly code to work with Windows x64. Building on this, I have compiled and deployed a new Windows x64 lasievef v5 app. If you are using Windows x64, you may see these workunits running. Please let me know if you encounter problems.

Will the v5 have its own Badge ? Thanks

---

No. v5 simply refers to version 5 of the sieving codebase, which supports an extended sieving range. My goal is to over time eliminate the version 4 apps, so eventually the separate v5 label will go away.

The badges are based on the size of the sieving area, which roughly equates to the size of number it is capable of sieving. Hence the 14e, 15e, and 16e badges.

BTW, this is why both 16e and 16e V5 contribute to the same badge, even though they show as separate apps.

Other than 5.1.10, 16e Lattice Sieve 5.1.11 transfers the CPU time into the runtime, when no runtime is given. Imo. this is an improvement.

I see a difference in memory use that give's me a problem;
I have set project preferences to accept only Lasieve5f.
I know it can uses up to 1 Gig memory per core.
My main pc (AMD 6 core 1090T)has 8 GB memory, so no problem running 6/time.
My laptop (i7 8 core/hyp) has 4 GB memory, so can do 3/time with some overhead.
Then I noticed a difference in memory use with different tasknames;
G6p401_ uses 500kB
G2L2590_ uses 850kB
In the time there was only G6p401 available I set the laptop to use 6 cores.
But when it run into some G2L2590 it locked up because it hasn't enough mem.

So can you let me/us set this in project preferences?
Then I can make work for laptop and home for main pc or something like that.

Aad