Shane Peelar

Found when it was added: https://github.com/clearlinux/autospec/blame/a5260d7ce751774d46e0a957786d179456a14275/autospec/buildpattern.py It was added by @fenrus75 for "high speed cases". Interesting.

I notice that on packages that are optimized for size, they enable `-ffunction-sections` and `-fdata-sections` for dead code removal, along with a `-Wl,--gc-sections`. However, these are two flags I want...

After researching a bit more, it looks like `-Wl,--gc-sections` is a weak form of LTO, and it is often compared to full LTO like GentooLTO uses. I'm not sure if...

OK -- so locally, I have enabled `-fno-common` and `-fno-semantic-interposition` and have started building a few packages with them. I'll try them out for a few days before pushing them....

OK -- I think i figured it out: https://software.intel.com/en-us/forums/intel-c-compiler/topic/635646 For more info: https://lkml.org/lkml/2015/5/19/1009 It looks like the historical reason for `-falign-functions=16` is: > The instruction fetch unit can fetch a...

Heh, of course the GCC devs beat me to the punch. https://github.com/gcc-mirror/gcc/commit/bc9f52f574c9dd2f620c12a5c651310327374da6 It looks like they are reworking the `-flimit-function-alignment` stuff in the next GCC version, given the commit message.

Thanks! In GCC trunk, we have this nice thing: ~~~ { /* N2[:M2] is not specified. This arch has a default for N2. Before -falign-foo=N:M:N2:M2 was introduced, x86 had a...

Okay, it is documented and I simply didn't look hard enough. It's hard to retain the old behaviour with the new method, since the secondary alignment will only be triggered...

Got a response from Arjan van de Ven! > without going into too many cpu microarchitecture details... Intel cpus like hot code to start at a 32 byte boundary. Very...

@sjnewbury: `-mtls-dialect` is a nice one! `-malign-data=cacheline` too. I got the impression that `-malign-data`, if changed, may not be compatible with code compiled with GCC 4.8 or older. Do you...