Quote from: joblo on February 28, 2017, 05:05:01 PM

Thanks. That was a lot of work, very much appreciated. It will help with my testing.
I don't often test for these architectures.

Edit:

I've tested the algos that failed for you on a i7-6700K compiled with gcc 4.8 using -march=core2 and they work.
You can retest hmq1275 in the next release. Some of the other algos have the same bug that caused x11 to crash
on Windows (The x11 bug affected only AVX2, not an issue on your x2). How did those algos fail?
Did the miner crash? Produce rejects? Do something else?

I'm trying on an Athlon64 X2 4000+ with gcc-5.2.1 using CFLAGS "-fomit-frame-pointer -Ofast -march=core2 -Wall". I made a super quick and dirty Python script which assumes that the algo works if it can run in the benchmark for 10 seconds:

- axiom: Fail
- bastion: Fail
- blake: OK
- blakecoin: Fail
- blake2s: OK
- bmw: Fail
- c11: Fail
- cryptolight: OK
- cryptonight: OK
- decred: OK
- deep: OK
- drop: OK
- fresh: Fail
- groestl: OK
- heavy: Fail
- hmq1725: Fail
- hodl: OK
- keccak: Fail
- lbry: OK
- luffa: Fail
- lyra2re: OK
- lyra2rev2: OK
- lyra2z: Fail
- lyra2zoin: Fail
- m7m: OK
- myr-gr: OK
- neoscrypt: OK
- nist5: OK
- pluck: Fail
- pentablake: OK
- quark: OK
- qubit: Fail
- scrypt: OK
- scryptjane:nf: Fail <- Not sure how to test this.
- sha256d: OK
- shavite3: Fail
- skein: OK
- skein2: OK
- timetravel: Fail
- vanilla: Fail
- veltor: Fail
- whirlpool: Fail
- whirlpoolx: Fail
- x11: Fail
- x11evo: Fail
- x11gost: Fail
- x13: Fail
- x14: Fail
- x15: Fail
- x17: Fail
- xevan: Fail
- yescrypt: Fail
- zr5: OK

When failing it's always "Illegal instruction (core dumped)".

Quote

CPU:
CPU features: SSE2
SW built on Mar 1 2017 with GCC 5.2.1
SW features: SSE2
Algo features: SSE2
Start mining with SSE2