| 1 |
On Tue, 20 Jan 2015 12:17:35 -0800 Christopher Head wrote: |
| 2 |
> On January 20, 2015 12:47:03 AM PST, Alexis Ballier <aballier@g.o> wrote: |
| 3 |
> >So, you're telling me that if you have a list of 90 cpu extensions, you |
| 4 |
> >will from time to time open that list to see if there is a 91st one |
| 5 |
> >added ? I think most people won't even notice, at best they'll look for |
| 6 |
> >the changelog. |
| 7 |
> |
| 8 |
> No, actually, I’m advocating the exact opposite. I’m saying that, as long as the list file is kept up to date, then I will look at those 90 flags when I first install and never again. If a 91st flag appears some day, then as long as the file was maintained as I described in an earlier message (i.e. flags are added as soon as manufacturers announce features), I already know I can reliably ignore the new flag. After all, if the flag didn’t exist when I installed the system, then my CPU must necessarily not have that feature—unless CPUs are in the habit of sprouting new instructions after you buy them! |
| 9 |
|
| 10 |
Not exactly. CPUs are not in a habit, but software is. Some brand |
| 11 |
new instuction set may be supported in (any of) packages with some |
| 12 |
delay. Thus it is possible that instruction set supported by your |
| 13 |
CPU will appear in the list of cpu flags after your ininial install. |
| 14 |
|
| 15 |
Best regards, |
| 16 |
Andrew Savchenko |
Archives