[QUOTE=emiller;595565]Is it possible to get a Mac OS 64 bit version or instructions for how to compile?[/QUOTE]

Try this: [url]https://www.dropbox.com/s/xo7psmmjfkb52pr/p95v303b6.MacOSX.tar.gz?dl=0[/url]

It is version 30.3 command line version which supports PRP proofs. As always, only for Intel CPUs.

Thanks for the link but this version is giving me the following:

[CODE]dyld: Symbol not found: _curl_mime_init
Referenced from: /Users/emiller/prime95/p95v303b6.MacOSX/./mprime
Expected in: /usr/lib/libcurl.4.dylib

Abort trap: 6[/CODE]

I found a link to this build earlier, thought I'd ask if there was a more recent build.

Maybe a build with only static linking?

[QUOTE=emiller;595593]Thanks for the link but this version is giving me the following:

[CODE]dyld: Symbol not found: _curl_mime_init
Referenced from: /Users/emiller/prime95/p95v303b6.MacOSX/./mprime
Expected in: /usr/lib/libcurl.4.dylib

Abort trap: 6[/CODE]

I found a link to this build earlier, thought I'd ask if there was a more recent build.[/QUOTE]

I just built 30.7 build 9. It likely has the same libcurl problem. If so, let me know and I'll see if static linking is possible.

[QUOTE=Prime95;596975]I just built 30.7 build 9. It likely has the same libcurl problem. If so, let me know and I'll see if static linking is possible.[/QUOTE]Available here, if that wasn't immediately apparent:
[url]https://mersenne.org/ftp_root/gimps/p95v307b9.MacOSX.tar.gz[/url]

[QUOTE=emiller;596313]Maybe a build with only static linking?[/QUOTE]

I think I figured out how to do this, please report on whether it worked.

A small advice to the Prime95 software
 

In the Prime95 software, when I clicked on 'Advanced--ECM', the default setting of the 'number to factor' is 2^1061-1. However, this number has been completely factored roughly ten years ago, so I wish the default could be changed to 2^1277-1, which is currently the smallest Mersenne composite that we haven't found any factors of.

[QUOTE=congsz;597547]In the Prime95 software, when I clicked on 'Advanced--ECM', the default setting of the 'number to factor' is 2^1061-1. However, this number has been completely factored roughly ten years ago, so I wish the default could be changed to 2^1277-1, which is currently the smallest Mersenne composite that we haven't found any factors of.[/QUOTE]
Yes, but millions of GHZ-days have already been spent on that exponent with no factor found. the smallest factor might be at least 2^300.
Maybe no default number?
(Happy to see another Chinese user :bounce:)
[spoiler](ps: why don't you suggest 2^1949001-1 ....)[/spoiler]

Segmentation fault on Debian Linux
 

Not very popular case, P-1 then TF-LMH, but still. Version mprime-30.7b9 on Linux Debian on 4-core E3-1240 v6 CPU crashes when completing P-1 and switching to trial factoring.
My configuration has 1 worker and 4 cores.

worktodo.txt
PFactor=3D003848AAF4D766D47DC6759098C9B1,1,2,108611647,-1,77,2
Factor=621092F3083ADEA698FF551DF07864ED,238617823,73,74

When trying to send the result to server and switch from 4 threads on P-1 (one main, three helpers) to 8 threads on TF the application crashes.

./mprime -d -c

This reports the completed work unit to server leaving only Factor= in the worktodo.

./mprime -d

[Main thread Jan 16 06:28] Mersenne number primality test program version 30.7
[Main thread Jan 16 06:28] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 4x256 KB, L3 cache size: 8 MB
[Main thread Jan 16 06:28] Starting worker.
[Work thread Jan 16 06:28] Worker starting
[Work thread Jan 16 06:28] Setting affinity to run worker on CPU core #1
[Work thread Jan 16 06:28] Setting affinity to run helper thread 1 on CPU core #1
[Work thread Jan 16 06:28] Setting affinity to run helper thread 3 on CPU core #2
[Work thread Jan 16 06:28] Setting affinity to run helper thread 5 on CPU core #3
[Work thread Jan 16 06:28] Setting affinity to run helper thread 7 on CPU core #4
[Work thread Jan 16 06:28] Starting trial factoring of M238617823 to 2^74
[Work thread Jan 16 06:28] Setting affinity to run helper thread 2 on CPU core #2
Segmentation fault

Manually run TF on mfaktc on Windows, so no work unit is lost.

Could somebody please look at the Seg fault issue.

With an AVX512F capable processor I see 2 to 4 % lower iteration times on bigger exponents using a 3200 K FFT than lower exponents using a 3136 K FFT. I could force the FFT length.
As far as I know, the benchmarks do not test different FFT length for a given exponent.

[QUOTE=pyajve;598068]Version mprime-30.7b9 on Linux Debian on 4-core E3-1240 v6 CPU crashes when completing P-1 and switching to trial factoring.

Could somebody please look at the Seg fault issue.[/QUOTE]

Will be fixed in next 30.8 build. Only affects TF using the AVX-512 instruction set. It is an assembler bug with an easy workaround.