[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171203162256.4ea0750d@vmware.local.home>
Date: Sun, 3 Dec 2017 16:22:56 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Trond Myklebust <trondmy@...marydata.com>
Cc: "linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"elfring@...rs.sourceforge.net" <elfring@...rs.sourceforge.net>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>
Subject: Re: Difficulties for compilation without extra optimisation
On Sun, 3 Dec 2017 15:17:32 +0000
Trond Myklebust <trondmy@...marydata.com> wrote:
> > I would like to check corresponding build results then without extra
> > optimisation applied by the compiler.
> > But I got surprised by error messages for a command like the
> > following.
> >
> > elfring@...ne:~/Projekte/Linux/next-patched> my_cc=/usr/bin/gcc-7 &&
> > LANG=C make -j4 CC="${my_cc}" HOSTCC="${my_cc}" EXTRA_CFLAGS='-O0'
> > allmodconfig fs/nfs/write.o
Why would you compile the kernel without optimization? There's many
places in the kernel that WILL NOT BUILD without optimization. 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.
-- Steve
Powered by blists - more mailing lists