From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Trevor Woerner <trevor.woerner@linaro.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: using Clang Was: Minutes: Yocto Project Technical Team Meeting - Tuesday, November 05, 2013
Date: Wed, 6 Nov 2013 14:00:01 -0500 [thread overview]
Message-ID: <527A91B1.3070708@windriver.com> (raw)
In-Reply-To: <CALmOhgnQ29+TvdGJ-7R=5wj-7zOx6LR8kn8c1vv6kzxz0hNkDQ@mail.gmail.com>
On 13-11-06 01:56 PM, Trevor Woerner wrote:
> On 5 November 2013 15:44, Liu, Song <song.liu@intel.com> wrote:
>> - Randy: Any plan to add Clang? open source compiler. Developed by Apple.
>> Qualcomm is working on it. RP: there are lots of other things. Not hearing
>> from tens of users on this. Welcome others to contribute.
>
> I'm curious to try Clang with OE too, but the last time I checked it
> still is not possible to build a valid kernel using Clang alone.
> Therefore I would assume if I wanted to use Clang it could only be for
> building user-space things and I'd still need a cross-gcc compiler for
> the kernel. Is that the current plan?
If we were to do it, I'd arrange to have enough of the patches from the
Clang team in the yocto kernel, to provide a valid building kernel. i.e.
it is possible now, just not with a stock kernel.
But it's all theoretical at the moment, since we aren't actually close
to trying anything yet :)
Bruce
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2013-11-06 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:56 using Clang Was: Minutes: Yocto Project Technical Team Meeting - Tuesday, November 05, 2013 Trevor Woerner
2013-11-06 19:00 ` Bruce Ashfield [this message]
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=527A91B1.3070708@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=trevor.woerner@linaro.org \
--cc=yocto@yoctoproject.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.