From: Borislav Petkov <bp@alien8.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Amy Parker <enbyamy@gmail.com>,
linux-kernel@vger.kernel.org, linux-gcc@vger.kernel.org,
linux-kbuild@vger.kernel.org, Michael Matz <matz@suse.de>
Subject: Re: Alternative compilers to GCC/Clang
Date: Tue, 2 Feb 2021 22:20:48 +0100 [thread overview]
Message-ID: <20210202212048.GG18075@zn.tnic> (raw)
In-Reply-To: <20210202210039.GB29751@1wt.eu>
+ Micha.
On Tue, Feb 02, 2021 at 10:00:39PM +0100, Willy Tarreau wrote:
> On Tue, Feb 02, 2021 at 09:19:20PM +0100, Borislav Petkov wrote:
> > On Tue, Feb 02, 2021 at 11:11:32AM -0800, Amy Parker wrote:
> > > On Tue, Feb 2, 2021 at 8:26 AM Amy Parker <enbyamy@gmail.com> wrote:
> > > > > It compiles extremely fast, implements some subsets of gcc (a few
> > > > > attributes for example), but is far from being able to compile a kernel
> > > >
> > > > Well, we'll see what I can do with that. :)
> > >
> > > Well, just installed it and tried building the kernel. Fails every file. :)
> > >
> > > It's definitely something to work towards - but I don't know if kernel
> > > advancements requiring newer GCC versions will go slow enough to allow
> > > TCC improvements to arise. This isn't just something like with Clang
> > > where a few tweaks to files and to Clang itself did the trick.
> >
> > Maybe this'll help you find something to do:
> >
> > https://www.youtube.com/watch?v=iU0Z0vBKrtQ
> >
> > Yes, it would be lovely to be able to compile the kernel with tcc but it
> > is not going to be trivial.
>
> In any case there will always be numerous limitations, but at least being
> able to perform the basic build check with limited options could save quite
> some time to many developers. Using gcc once the tcc-based "typo check"
> passes would already be a nice start. Getting the kernel to boot would
> indeed be a huge step forward! In haproxy we can only build with threading
> disabled and it works slowly but sufficiently for basic tests and printf-
> based debugging. It's convenient for bisecting certain bugs.
>
> Thanks for the video Boris, I wasn't aware of it, definitely interesting!
Yeah, and there's a repo with that stuff:
https://github.com/susematz/linux
and also:
https://github.com/susematz/linux/blob/tcc46/README.tcc
It would be good to start forward-porting and integrating some of the
fixes and even extend tcc to handle some of the gnuisms we're using in
the kernel so that we can build the kernel with it too.
I can imagine having CONFIG_TCC - as long as that doesn't get too
intrusive and get in the way of things - and those who wanna build the
kernel with it, can enable it. For example...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-02-02 21:20 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
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 [this message]
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=20210202212048.GG18075@zn.tnic \
--to=bp@alien8.de \
--cc=enbyamy@gmail.com \
--cc=linux-gcc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--cc=w@1wt.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).