mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grozdan <neutrino8@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux and LLVM
Date: Fri, 8 May 2009 21:50:04 +0200	[thread overview]
Message-ID: <c5bd819b0905081250k2095beb6r1aae22fcd82ac468@mail.gmail.com> (raw)
In-Reply-To: <4A048AF4.1080205@garzik.org>

2009/5/8 Jeff Garzik <jeff@garzik.org>:
> Grozdan wrote:
>>
>> Hi,
>>
>> First, I'd like to say that I'm not interested in any holy wars,
>> trolling, ego-boosters, or whatever, and basically want to ask a
>> simple question and get the views of the Linux developers on it, at
>> least from those who are interested in answering it or have time to do
>> so as I know that most kernel devs are very busy :)
>>
>> Recently, FreeBSD has reported that it's slowly switching from GCC to
>> LLVM/CLANG for compilers. What are the thoughts of the Linux kernel
>> devs about this and do they things that it's a good idea to go in the
>> same direction as FreeBSD (switching over to LLVM)?
>
> It is highly unlikely we will switch compilers away from gcc -- we have
> enough problems just supporting multiple gcc versions.
>
> That said, you could join the effort to get LLVM to compile under the
> kernel.  Here is a meta-bug for that:
> http://llvm.org/bugs/show_bug.cgi?id=4068
>
> It is a moot question until LLVM can actually build a bootable kernel :)

Thanks for the quick answer! I was not aware that currently there's
lots of work until CLANG can compile a bootable Linux kernel. Thanks
for the link too. I'll dig through it

>
> Regards,
>
>        Jeff
>
>
>
>

  reply	other threads:[~2009-05-08 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 19:28 Grozdan
2009-05-08 19:41 ` Jeff Garzik
2009-05-08 19:50   ` Grozdan [this message]
2009-05-09  9:13     ` Theodore Tso

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=c5bd819b0905081250k2095beb6r1aae22fcd82ac468@mail.gmail.com \
    --to=neutrino8@gmail.com \
    --cc=jeff@garzik.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 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®