Quote from: Roolieman on June 02, 2016, 06:53:36 AM

Quote from: joblo on June 01, 2016, 11:26:42 PM

Quote from: Roolieman on June 01, 2016, 10:27:03 PM

Cpuminer is working and Im planing to use it on some xeon servers.
On Haswell Xeon it works like charm but cpuminer-opt-3-3-2-windows is not working on Westmere Xeon, I've got error message asking me to recompile. Same error on some older Xeons, with only SSE2 support.
Can some good soul explain how to do that.

Which model CPU do you have and can you confirm it has both AES_NI and AVX.
The rebuild message you saw was changed in v3.3.2 to also check for AVX. This
means the miner thinks the CPU has AVX as well as AES_NI, need to confirm that.

If the miner is wrong it's a bug I need to investigate.

If your CPU does indeed have AES_NI and AVX then the message is correct and the
Westmere build was not compiled with AES-AVX1 support.

In the meantime you can ignore the message and keep mining.

Edit:
The best thing to do, IMO, is to install mingw on your Westmere and compile for youself for
the native architecture. This should ensure you get an optimum build regardless if your CPU
has AVX1 or not, assuming the capabilities check is working properly. If not it will help define
the problem better.

As I said I don't have the proper CPU to test with so I'm dependent on users like you to confirm
the AVX1 check is working properly. I appreciate your time and efforts.

I recommend this to any users with CPUs in the grey zone between core2 and Sandybridge.

Hello Joblo thx for help.
I will try to describe all scenarios I have, feel free to ask anything.

First server has 2 Xeon E5540 (Gainestown), only SSE instructions (no AES, no AVX). Error that it throws:

Checking CPU capatibility...
   Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
   CPU arch supports AES-AVX1...NO.
   CPU arch supports SSE2.....YES.
   SW built for SSE2..........NO.
Incompatible SW build, rebuild with "-march=native"

Second server has 2 Xeon E5649 (Westmere-EP), SSE, AES (no AVX). Error that it throws:

Checking CPU capatibility...
   Intel(R) Xeon(R) CPU E5649 @ 2.53GHz
   CPU arch supports AES-AVX1...NO.
   CPU arch supports SSE2.....YES.
   SW built for SSE2..........NO.
Incompatible SW build, rebuild with "-march=native"

Third server has 2 Xeon E5-2687W v3 (Haswell E/EP), SSE, AES, AVX2, and it works like charm throwing around 2 MH/s.
On this one I'm using cpuminer-haswell-broadwell.exe
(For some reason I have to start two separate miners for both processors to fire)

Checking CPU capatibility...
   Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz
   CPU arch supports AES-AVX1...YES.
   SW built for AES-AVX1........YES.
   Algo supports AES-AVX1.......YES.
Start mining with AES-AVX1 optimizations...
[2016-06-01 23:44:35] 20 miner threads started, using 'x11evo' algorithm.

I have also tested miner on my gaming rig with i5-2500K where it also works throwing around 200KH/s, using cpuminer-sandybridge-ivybridge.exe

On servers where miner fails I have tried all executables but with same error.

Can you pls point me to some tutorial about using mingw and link to source code?

Thank you very much for the detailed data. It is very helpful. The main problem is this line:
" SW built for SSE2..........NO.". This is supposed to indicate how it was compiled. I tried
the precompiled Westmere binary on my Skylake and it said it was compiled for SSE2.
Another user reported the same problem with a Nehalem CPU.

I encourage you to try to use mingw. There are instructions in the README.md file.
If you have problem you can always post questions in the cpuminer-opt thread.

I'm fed up with those cpability checks. They were supposed to help users but have had the
opposite effect. It will be removed from v3.3.4.

I'll wait a litle longer to ensure there are no other issues with v3.3.3