From: anton@mips.complang.tuwien.ac.at (Anton Ertl)
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc] built-in native compiler for Linux?
Date: Thu, 23 Apr 2009 20:22:24 GMT [thread overview]
Message-ID: <2009Apr23.222224@mips.complang.tuwien.ac.at> (raw)
In-Reply-To: <20090422085828.GA16917@elte.hu>
Ingo Molnar <mingo@elte.hu> writes:
> Furthermore, a lot of optimizations in GCC are driven by
>SPECint and SPECfp benchmarketing, with little practical relevance
>to 99% of the apps, including the kernel.
Right, and it's not just the kernel that has to work around GCC
breakage, it's also many apps (possibly all of them except SPEC
benchmarks, and the few 100% C99-compliant programs (probably none
with more than than 500 lines of code)).
So I guess a decent alternative to GCC would attract not just the
kernel people, but also many (most?) applications people. Then GCC
would no longer be misused for ordinary applications or kernels and it
could focus on its true destiny: compiling SPEC benchmarks.
Whether to build such a compiler mostly from scratch as you suggest or
as a fork of GCC is up to whoever does it. The GCC fork variant has
the advantage of having a lot of targets available already, but the
disadvantage of a large and complex code base.
- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html
next prev parent reply other threads:[~2009-04-23 20:39 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 [this message]
[not found] ` <alpine.DEB.1.10.0904241429450.19686@qirst.com>
2009-04-25 5:29 ` David Miller
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=2009Apr23.222224@mips.complang.tuwien.ac.at \
--to=anton@mips.complang.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®