From: David Miller <davem@davemloft.net>
To: cl@linux.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc] built-in native compiler for Linux?
Date: Fri, 24 Apr 2009 22:29:52 -0700 (PDT) [thread overview]
Message-ID: <20090424.222952.83381016.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0904241429450.19686@qirst.com>
From: Christoph Lameter <cl@linux.com>
Date: Fri, 24 Apr 2009 14:34:49 -0400 (EDT)
> On Wed, 22 Apr 2009, Ingo Molnar wrote:
>
>> What i think makes sense is to build a _new_ precompiler / compiler
>> / assembler / linker combo for Linux, from scratch, hosted in the
>> kernel proper.
>>
>> A good technical basis for that would be Sparse, and it could start
>> by acting as a drop-in replacement for CPP and it could feed its
>> output to GCC with little changes. Sparse is small, has a very tidy
>> code base and is already useful today as an extended static source
>> code checker.
>
> A new preprocessor would be great. If we can make sparse do what CPP does
> now then lets go for it.
It's just too bad that we'll lose the performance gained from the
fact that GCC's CPP is linked into the C compiler binary and thus
doesn't have to transfer it's result over a pipe or anything like
that.
I really think this whole idea isn't a very smart one. I would
rather have whoever would be working on a sparse backend instead
be working on kernel improvements.
I also think people underestimate how much work this would be.
next prev parent reply other threads:[~2009-04-25 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 8:58 Ingo Molnar
2009-04-23 20:22 ` Anton Ertl
[not found] ` <alpine.DEB.1.10.0904241429450.19686@qirst.com>
2009-04-25 5:29 ` David Miller [this message]
2009-04-25 7:06 ` Eric W. Biederman
2009-04-27 13:52 ` Christoph Lameter
2009-04-27 17:34 ` Al Viro
2009-04-27 18:41 ` Eric W. Biederman
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=20090424.222952.83381016.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cl@linux.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®