On Mon, 4 Dec 2017 10:00:54 +0100 SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx> wrote: > > Why would you compile the kernel without optimization? > > Can another reason be occasionally still relevant? No. > > Will the compilation be a bit quicker when extra data processing > could be omitted? Why would you care more about the time it takes to compile the kernel, than the time it takes for executing it? Benchmarks are all about performance of a running kernel, nobody compares benchmarks of the time it takes to compile it. Sure, we like to make the compile times quicker (heck, I wrote "make localmodconfig" for just that purpose), but we never favor compiler time over execution time. In fact, if we can improve the execution performance by sacrificing compile time, we are happy to do that. > > > > There's many places in the kernel that WILL NOT BUILD without optimization. > > Would you like to keep the software situation in this way? Yes. > > > > In fact, we do a lot of tricks to make sure that things work the way > > we expect it to, because we add broken code that only gets compiled out > > when gcc optimizes the code the way we expect it to be, > > and the kernel build will break otherwise. > > * Can this goal be also achieved without the addition of “broken code”? No. > > * How do you think about to improve the error handling there? It works just fine as is. Errors that can be detected at build time are 100 times better than detecting them at execution time. -- Steve -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
