From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: changing parameters in build
Date: Wed, 17 Oct 2018 13:55:29 +0200 [thread overview]
Message-ID: <20181017115529.GA323@kroah.com> (raw)
In-Reply-To: <CALS6=qWKto5tMjLLwemWx9b68Uc0+fy-3dPPJK1QUstAQy6D2Q@mail.gmail.com>
On Wed, Oct 17, 2018 at 04:24:13PM +0800, Carter Cheng wrote:
> Hi,
>
> I am having exploring how much work it would be to do whole kernel
> optimization using clang on the current kernel. My understanding is the
> kernel uses a recursive make file system. I am curious if there are any
> easy ways to get the kernel to build llvm bit code for all files without
> going through and hand editing hundreds of makefiles.
There is no need to modify more than one makefile. Look at how the
kernel is built, you should be just fine as-is because people use clang
just fine today.
good luck!
greg k-h
next prev parent reply other threads:[~2018-10-17 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 8:24 changing parameters in build Carter Cheng
2018-10-17 11:55 ` Greg KH [this message]
2018-10-17 12:02 ` Carter Cheng
2018-10-17 12:12 ` Greg KH
2018-10-17 12:13 ` Carter Cheng
2018-10-17 13:05 ` valdis.kletnieks at vt.edu
2018-10-17 13:11 ` Carter Cheng
2018-10-17 13:18 ` Carter Cheng
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=20181017115529.GA323@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).