From ArchWiki
Revision as of 01:54, 1 April 2016 by Silverhammermba (talk | contribs) (-march=native VS -march=broadwell: re)
Jump to navigation Jump to search

-march=native VS -march=broadwell

currently, I'm working on fix this problem [1].

how I have written in that topic, -march models could not be updated to your true CPU architecture i.e. there are many versions of core2 CPU and -march=core2 would be conservative. In this direction I'm going to add a warning box in this page. Let me know if it's a good idea!

—This unsigned comment is by NTia89 (talk) 10:10, 31 March 2016‎. Please sign your posts with ~~~~!

What would be the warning about? The wiki recommends -march=native, which enables more tweaks than (in your case) -march=broadwell, as expected. -- Lahwaacz (talk) 13:15, 31 March 2016 (UTC)
Sorry, where? --nTia89 (talk) 13:21, 31 March 2016 (UTC)
In Makepkg#Creating_optimized_packages. Given that you started the discussion here, I was assuming that you're aware of the section... -- Lahwaacz (talk) 15:38, 31 March 2016 (UTC)
No, I don't read what I want to add, nowhere is stated that "It is suggested to keep -march=native and not substitute it with your specific CPU architecture because, in order to maintain the compatibility with the whole CPU architecture series, sometimes some optimization are disabled even if your actual CPU which belong to a certain CPU architecture, supports it."--nTia89 (talk) 16:04, 31 March 2016 (UTC)
These things are out of scope for the makepkg article, which is a general overview of how to use CFLAGS in makepkg.conf. The gentoo wiki is better suited for these things, and we link to it already. -- Alad (talk) 20:42, 31 March 2016 (UTC)
The article already mentions that native enables optimizations specific to your hardware. I thought it was pretty obvious that that would provide a better result than any specific march flag. But it wouldn't hurt to make that paragraph a little more explicit. Silverhammermba (talk) 01:54, 1 April 2016 (UTC)