On Mon, Aug 01, 2016 at 11:08:47PM +0200, David Seifert wrote: > Dear friends, > while version bumping sci-libs/fftw, I've noticed our CPU_FLAGS_X86 > list could be expanded a bit:
I like the idea of expanding the list of CPU_FLAGS_X86, and having flags for other arches too, but I would be in favor of dropping the _X86 suffix and using CPU_FLAGS for all arches. Your machine most likely will only have one kind anyway. Not sure what others think about it, though. > avx512 - introduced with Skylake and Knights Landing Only Skylake Xeons (yet to be launched) will support AVX512, and as mentioned in another email, the subsets supported by Skylake and KNL are a bit different. So, adding each subset should be better (e.g. avx512f, avx512cd, avx512er, etc). > I also propose creating a CPU_FLAGS_PPC variable containing (at least): > > altivec - PowerPC's SSE > vsx - PowerPC's AVX > > Finally, I also propose creating CPU_FLAGS_ARM variable containing: > > neon > > Any ideas? Currently cpu-feature flags for non-x86 are package local, > whereas making them globally available makes masking easier for non- > applicable archs etc. and makes enabling them easier for users. Masking flags is not needed if they are determined from /proc/cpuinfo. Cheers, —Guilherme
