Difference between revisions of "Optimizing built binaries"

From postmarketOS
Jump to navigation Jump to search
(Created page with "A compiler can be told to create binaries specifically for one CPU or family of CPUs, often resulting in a (minor, albeit always welcome) performance boost. On weaker systems,...")
 
m (Konradybcio moved page Optimizing the kernel binary to Optimizing built binaries: Passing optimization flags to the kernel isn't correct and shouldn't really be done.)
 
(One intermediate revision by one other user not shown)
Line 9: Line 9:
 
* [https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#ARM-Options GCC documentation: ARM options]
 
* [https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#ARM-Options GCC documentation: ARM options]
 
* [https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html#AArch64-Options GCC documentation: aarch64 options]
 
* [https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html#AArch64-Options GCC documentation: aarch64 options]
 +
 +
[[Category:Technical Reference]]

Latest revision as of 19:39, 20 January 2020

A compiler can be told to create binaries specifically for one CPU or family of CPUs, often resulting in a (minor, albeit always welcome) performance boost. On weaker systems, every additional bit of performance might be significant to the user.

Reference