| 1 |
On January 14, 2015 7:16:46 AM PST, Alexis Ballier <aballier@g.o> wrote: |
| 2 |
>however, i disagree with your rationale: asm for specific cpu |
| 3 |
>extensions tend to be written and tested after given cpu is available, |
| 4 |
>thus if you have a brand new cpu, you want to be notified if a package |
| 5 |
>gains support for this new instruction set |
| 6 |
|
| 7 |
Do people really want to be notified if a package gains support for a new instruction set? I know I don’t. I would rather have all possible instruction set extensions available as flags and set whichever ones my CPU has once, at install time. If a package gains support for an extension later, then whenever it upgrades, it will just work, because the relevant flag will already be set in make.conf from back when I installed Gentoo on the box. |
| 8 |
|
| 9 |
For this to work right requires that a dev add all the extensions to the flag before I buy the CPU. All that requires is knowing the names, though; it would be fine if no package actually uses the feature yet. |
| 10 |
|
| 11 |
-- |
| 12 |
Christopher Head |
Archives