Someone ran into this on Discord, so adopt the same workaround that chrome did, by checking both OSXSAVE and XSAVE before calling XGETBV. The old way of detecting AVX is correct per Intel, but such is life.
Someone ran into this on Discord, so adopt the same workaround that chrome did, by checking both OSXSAVE and XSAVE before calling XGETBV. The old way of detecting AVX is correct per Intel, but such is life.