CPU_FLAGS_X86 is USE_EXPAND, so it's global by definition. Adding additional local flags is both technically wrong, and harms users by not having them properly defined globally. dev-libs/nettle/metadata.xml: <flag name="cpu_flags_x86_sha">Enable support for Intel's SHA instruction set (SHA-NI)</flag> media-libs/babl/metadata.xml: <flag name='cpu_flags_x86_f16c'>Take advantage of CPU feature f16c</flag> media-libs/openimageio/metadata.xml: <flag name="cpu_flags_x86_avx512f">SIMD Optimization</flag> media-libs/openimageio/metadata.xml: <flag name="cpu_flags_x86_f16c">SIMD Optimization</flag> media-libs/osl/metadata.xml: <flag name="cpu_flags_x86_avx512f" restrict=">=media-libs/osl-1.9.0"> media-libs/osl/metadata.xml: <flag name="cpu_flags_x86_f16c" restrict=">=media-libs/osl-1.9.0"> I think I've CC-ed all people responsible for adding them. Now please kindly send patches to -dev making them global flags properly, and since you failed to follow policy in the first place, please kindly send patches to cpuid2cpuflags [1] as well. [1] https://github.com/mgorny/cpuid2cpuflags
All gone. The vandalism related to sha flag removal will be handled separately.