Closed jhallard closed 4 years ago
It looks like the same bug as #133. I'm still working on a new way to see why this is happening, but have been very busy lately. Any help with this would be appreciated.
I might be able to help out a bit - one thing that is confusing to me is that I'm getting the flag avx1.0
as output from get_cpu_info['flags']
, but I don't see avx1.0
as a string anywhere in this repo? I'm not sure where that would be generated from.
I did some more research and found this project: https://github.com/Mysticial/FeatureDetector/blob/master/src/x86/cpu_x86.cpp
I built and ran the program 1000 times and it always reported AVX support as true, so I do believe that the issue exists only in this repo and is not some underlying OS error.
Closing this as it is a duplicate. See #133 for the original.
In your bug report please include:
CPU architecture Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
Operating System macOS Mojave Version 10.14
Python version 2.7.16.final.0 (64 bit)
Version of py-cpuinfo py-cpuinfo==5.0.0
I'm seeing the following behavior when trying to check for CPU flags on my MacBook
This is the output of the 61 flags
this is the output of the 74 flags
the one that really bothers me is that sometimes "avx" is included and sometimes it is missing, while "avx1.0" is always included