Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 158. (Read 444040 times)

thx for the hint

The logic in there is "AND" as requirement. Meaning both AVX and XSAVE have to be there. In cpuminer-opt it's "OR", meaning presence of either AVX or XSAVE will return has_avx()=true.

Thanks, this is good info. It might help with the other problem being discussed.

Checking CPU capatibility...
                  Intel(R) Xeon(TM) CPU 2.80GHz
CPU features: SSE2 AVX AVX2
SW built on Jun  5 2016 with GCC 5.3.0
Build features: SSE2
Algo features: SSE2 AES
AES not available, starting mining with SSE2 optimizations...

I am a noob in compiling, I have never done it. I thought that you are interested 

CMB hasn't compiled any builds for CPUs without AES. Some algos will still work on your CPU because they are not optimized
for AES. Please post the output at miner startup. If the algo says it has AES it will crash. If the algo doesn't have AES
it will work.

You will need to compile yourself to mine algos that have been optimized for AES. The instructions are in READSME.md.

I have downloaded it from cryptomining-blog website. There is a sse2 executable which is working fine with other algos.

CPUID status, will update with new info

Trying to fix a bug that isn't a bug just creates more bugs.

That's what happened with the AVX flag. The orignal implementation was correct. A detailed explanation
is avaiable in this file:

https://bitbucket.org/ariya/cpu-detect/src/cc2037e9bd0fb8cf12846dbfa4818fd813043972/base/cpu.h?at=master

So I've reverted.

The AVX2 flag isn't implemented by cpu-detect so I don't know if it requires the same logic ad AVX1. I will look into it further.

cpu_detect returns the AES flag directly from the cpuid register so it is still a complete mystery why it was misidentified
on the AMD Phenom2.

The owner of a Xeon without AES posted capabilities while attemting to use the CMB Westmere build and it showed some
interesting results. It correctly showed the CPU did not have AES but incorrectly displayed AVX and AVX2 as being
available.

This help define the problem, or should I say problems:

1. AVX shows available on non-AES CPU. This one might be understood and fixed with the correct reading of
this feature. I would need a volunteer with a non-AES CPU to test.

2. AES shows available on non-AES AMD CPU. Still a mystery but seems limited to AMD.

3. AVX2 shows available on non-AES CPUs. I have to reimplement this because it does not use cpuid.

I would like a volunteer or two because I don't like to publicly release code based on trial and error, which has
been happening for the past few releases. These volunteers would need to be able to compile their own, Windows
or Linux, doesn't matter. I hope I ave one volunteer already with an older AMD CPU. I would like a volunteer with
old Intel CPU particularly Westmere and Nehalem.

Investigation continues.

If you used the CMB binaries none of them support CPUs without AES, however cpuminer-opt does support
non-AES CPUs if you compile yourself. See README.md for instructions.

Hi, I was trying to mine x11evo algo with my older Xeon 7030 (codename Paxville) processor, but it crashed.  HOdl is working fine. The processor has has sse2 and sse3 capabilities.

Win bins now available:

http://cryptomining-blog.com/wp-content/download/cpuminer-opt-3-3-5-windows.zip

I'd like to get some feedback regarding the CPU capabilities check from other AMD users as well as
Nehalem and Westmere.

In particular:

- OS, build procedure, changes to default build.
- CPU capabilities output at miner startup.
- discrepencies between output and reality
- did miner work, did it work at expective performance level
- change in behaviour from previous releases
- anything else you may think is useful.

Some info can be confirmed with the following commands, piping to grep focusses
on specific info.

Display CPU info Linux. Maps to CPU HW capabilities.

cat /proc/cpuinfo
cat /proc/cpuinfo | grep AES

Display default gcc options, Linux and mingw.

gcc -Q -march=native --help=target
gcc -Q -march=native --help=target | grep march

@th3.rOOt, can you try this on your AMD, to see if it works? Thanks.

Edit: I looked at the cpu_detect code and it uses cpuid at its heart. Howver, for AVX it also checks the XSAVE
bit (the ones hmage thinks are a bug) and also checks a kernel var for XSAVE, not done by cpuminer-opt.

This may help explain why AVX was misidentified, but there's also AES and AVX2. In cpu_detect there is no
mention of AVX2 and AES has no special handling. Did CPU AES get misindentified in previous releases?

Different problem.

I didn't see much use in low level features or lib dependencies being listed.
I can easilly put them back, or I could even add more info to -V if you like.
I'm open to suggestions.

I'm still looking for some way the application can determine which -march was
used and maybe other compiler options. I tried reading CFLAGS and CXXFLAGS
but they are undefined in the application. I wonder if there is some way they can be passed
to the program during compilation?

There's cpuid — http://www.etallen.com/cpuid/cpuid-20151017.src.tar.gz


As you can see in the source code, AVX flag is just one-bit check from 1/ECX, not how it's done in cpuminer-opt.

cpuminer-opt definitely has a bug in AVX detection.

I did a little digging for "open source CPU feature identification"

Here's what I found - https://bitbucket.org/ariya/cpu-detect/src

When I run it on my Ubuntu boxes here's the result:


Even it compiled fine on Win7 MSYS+WinBuilds!

Maybe this will help to finally get correct CPU features and identifacation.

I compile it myself on my personal Win7 machine so I have CPU-Z installed.
cpuminer compilation with MSYS+WinBuilds like in README, without autogen.sh, because it fails on MSYS.
Also custom libcurl and openssl dll's compiled for other project.

Other thing...
cpuminer-opt 3.3.4 -V outputs dependency libs version

cpuminer-opt 3.3.5 -V outputs just this:

build.sh (or winbuild.sh for Windows) also works and sets the flags correctly.

I think I'll add a brief installation section to the OP. Perhaps that will reduce the number of these questions.
It seems to be becoming a FAQ.

Yes very weird. I haven't found anything to suggest they've implemented CPUID differently than Intel,
yet these flags are taken directly from the CPUID register.

I would be nice if CPUz had open source so I could just copy their code. I found this, closest I found
to your CPU. Something I can work with to figure out what's wrong.

http://users.atw.hu/instlatx64/AuthenticAMD0100F42_K10_Deneb_CPUID.txt.

Edit: Did you compile on a VM and run CPUz on the host?

Did you include CXXFLAGS="-std=gnu++11" in your configure?

There is some really weird stuff going on with CPU capabilities check on AMD...

According to cpuminer-opt binary:
AMD Phenom(tm) II X4 965 Processor
CPU features: SSE2 AVX AVX2
SW built on Jun  5 2016 with GCC 4.8.3
Build features: SSE2
Algo features: SSE2 AES
AES not available, starting mining with SSE2 optimizations...

According to CPUID CPU-Z:


I'm pretty sure that this is the problem with -march=native on AMD CPU's without AES-NI.