This caught my eye recently: "cryptest.exe reports wrong CPU features for Core2 duo", http://github.com/weidai11/cryptopp/issues/176. I think it managed to stay under the radar because most of the hardware today is fully featured.
I'm trying to craft a test for cryptest.sh to detect the condition, but its turning out to be tricky. We can parse the output of 'cryptest.exe v' and capture hasMMX, hasSSE2, etc. We can then compare it against what we expect from `-march=native` preprocessor macros when `-march=native` is available. However, the tricky part is capturing all the features in one execution of 'cryptest.exe'.
I was thinking we may want a 'cryptest.exe f' to dump the feature strings shown in this line: