From: Willy Tarreau <w@1wt.eu>
To: Amy Parker <enbyamy@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-gcc@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: Alternative compilers to GCC/Clang
Date: Tue, 2 Feb 2021 06:33:08 +0100 [thread overview]
Message-ID: <20210202053307.GB28542@1wt.eu> (raw)
In-Reply-To: <CAE1WUT6mp80yFDgAirZcKvc31O23ynpLGcsdPaa8qd1dsXiXhg@mail.gmail.com>
Hi Amy,
On Mon, Feb 01, 2021 at 03:31:49PM -0800, Amy Parker wrote:
> Hello! My name's Amy. I'm really impressed by the work done to make
> Clang (and the LLVM toolchain overall) able to compile the kernel.
> Figured I might as well donate my monkey hours to helping make it run
> on other compilers as well. I haven't been able to find any that use
> the same arguments structure as GCC and Clang (read: you can pass it
> in as CC=compilername in your $MAKEOPTS). Any compilers along that
> route anyone here has worked with that I could work with?
If you're interested, you should have a look at TCC (tiny CC) :
https://repo.or.cz/tinycc.git
It compiles extremely fast, implements some subsets of gcc (a few
attributes for example), but is far from being able to compile a kernel
(at least last time I checked). Its speed makes it very convenient for
development. I made some efforts to make haproxy support it (and provided
some fixes to tcc) as it compiles the whole project in 0.5 second instead
of ~10 seconds with a modern gcc. It could probably compile a kernel in
15-20 seconds if properly supported, and this could be particularly handy
for development and testing.
Regards,
Willy
next prev parent reply other threads:[~2021-02-02 5:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:31 Alternative compilers to GCC/Clang Amy Parker
2021-02-02 5:33 ` Willy Tarreau [this message]
2021-02-02 16:26 ` Amy Parker
2021-02-02 19:11 ` Amy Parker
2021-02-02 20:19 ` Borislav Petkov
2021-02-02 21:00 ` Willy Tarreau
2021-02-02 21:20 ` Borislav Petkov
2021-02-02 21:41 ` Willy Tarreau
2021-02-02 23:20 ` Michael Matz
2021-03-10 8:53 ` Pavel Machek
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=20210202053307.GB28542@1wt.eu \
--to=w@1wt.eu \
--cc=enbyamy@gmail.com \
--cc=linux-gcc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.