| 1 |
On Mon, Feb 2, 2015 at 4:43 PM, James <wireless@×××××××××××.com> wrote: |
| 2 |
> But, looking at : /usr/portage/profiles/desc/cpu_flags_x86.desc |
| 3 |
> I surmise: |
| 4 |
> |
| 5 |
> CPU_FLAGS_X86="mmx sse sse2 sse3 ssse3 sse4 sse4_1 sse4_2 sse4a ssse3 \ |
| 6 |
> mmx mmxext xop 3dnowprefetch 3dnow 3dnowext aes avx avx2 fma3 fma4 \ |
| 7 |
> padlock popcnt " |
| 8 |
> |
| 9 |
|
| 10 |
Exactly how did you "surmise" your list? |
| 11 |
|
| 12 |
> What would be cool, is if the devs took the entire list of cpu flags |
| 13 |
> from proc/cpuinfo and piped it thru a simple validation script (equery |
| 14 |
> hasuse) to generate the maximum flags to set by default for a given cpu. |
| 15 |
|
| 16 |
That's exactly what cpuinfo2cpuflags-x86 does. |
Archives