From: Steven Rostedt <rostedt@goodmis.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: Difficulties for compilation without extra optimisation
Date: Mon, 04 Dec 2017 09:48:42 +0000 [thread overview]
Message-ID: <20171204044842.0edbc51b@vmware.local.home> (raw)
In-Reply-To: <c834d3ed-3da3-e2b5-7f4b-9e36bfcb388b@users.sourceforge.net>
On Mon, 4 Dec 2017 10:00:54 +0100
SF Markus Elfring <elfring@users.sourceforge.net> 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
next prev parent reply other threads:[~2017-12-04 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:53 [PATCH RFC v1] nfs/write: Use common error handling code in nfs_lock_and_join_requests() SF Markus Elfring
2017-12-03 14:15 ` Difficulties for compilation without extra optimisation SF Markus Elfring
2017-12-03 15:17 ` Trond Myklebust
2017-12-03 21:22 ` Steven Rostedt
2017-12-03 21:56 ` SF Markus Elfring
2017-12-04 2:40 ` Steven Rostedt
2017-12-04 9:55 ` SF Markus Elfring
2017-12-04 9:00 ` SF Markus Elfring
2017-12-04 9:48 ` Steven Rostedt [this message]
2017-12-04 10:18 ` SF Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171204044842.0edbc51b@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).