g build for your CPU
using all CPU features you can use.
That's different from LLVM, which attempts to find which CPU most
closely matches yours. In that VM scenario, it would either disable
some features you could use or enable ones you can't.
Thanks for the interesting pointers, and both of your answers!
--
Kevin Weidemann
the commit correctly, the change that causes this
is the removal of `PTA_AES` in
const wide_int_bitmask PTA_WESTMERE = PTA_NEHALEM | PTA_AES | PTA_PCLMUL;
as PTA_IVYBRIDGE contains PTA_SANDYBRIDGE which in turn contains
PTA_WESTMERE.
Is this an oversight or mistake?
Best regards,
Kevin W
