On 8/21/24 12:34 AM, ralfconn wrote: > I did not know about this 'Microarchitecture level' definition [1], > thanks. I'd expect the -v3 to be a superset of the -v2, instead when in > the past I tried to boot a Ryzen 9 from a system built with > -march=native for an FX 8530 it did not work (I don't remember if it was > a kernel panic or if it stopped already at GRUB, I think the latter), so > I had to reinstall from stage 3. > > raffaele > > [1] https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels
Yup, that is the great advantage of these microarchitecture "common levels". Unlike -march=native which just toggles every single tiny option your current CPU supports, these are strictly defined supersets designed to work with, basically, "any CPU produced after a certain date". It makes it much easier to deliver common optimizations to a mere 3 distinct configurations. Also it makes it much easier to rapidly tell which group your current CPU supports. Gentoo's official binhost uses these too. Well, the binhost provides a regular generic -march=x86-64 set of binary packages, plus a set that targets the -march=x86-64-v3 seriesdsfe. No "v2" or "v4" packages there, I'm afraid. :) -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
