Surprisingly, -march=native doesn’t always expand to the locally optimal build flags we might expect, particularly with gcc on non-Linux platforms.

Oh interesting. Is this one of those things where backwards compatibility eventually got in the way of the intended purpose?

I actually do. I just said -march=tigerlake to make it clear what CPU family the compiler was targeting.