On January 20, 2015 12:47:03 AM PST, Alexis Ballier <aball...@gentoo.org> wrote: >So, you're telling me that if you have a list of 90 cpu extensions, you >will from time to time open that list to see if there is a 91st one >added ? I think most people won't even notice, at best they'll look for >the changelog.
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! >Isn't it better to have a script, e.g. in gentoo-x86/scripts (that >would be the first of this kind here I think), that would >"parse" /proc/cpuinfo and output 'CPU_FLAGS_...="..."' so that for a >first install you can simply send its output to make.conf and, if you >are paranoid, can use it to check if this has changed in a postsync >hook ? I see having a script to select flag values as orthogonal to when the flag values need to be looked at. I also agree that having a script would be a good thing. -- Christopher Head
