the set of over-optimizing app developers will do just that :) But more generally, optimizations eventually stop being true in general, and start being true on

the set of over-optimizing app developers will do just that :) But more generally, optimizations eventually stop being true in general, and start being true only in a specific context -- and the lower that optimization, the more specific that context gets. If you want to "teach" GCC how to optimize something properly (more commonly in the form of attribute notations e.g. inlining, but more extreme is poking around godbolt), you start falling into this trap