From: Tim Deegan <tim@xen.org>
To: Jeffrey Karrels <karrelsj@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Clang/LLVM version requirements
Date: Wed, 12 Sep 2012 11:31:45 +0100 [thread overview]
Message-ID: <20120912103145.GB97347@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAFw--Dche2NB0jjBdMyAYC=S92XkW9UpsaBsTRBcX4ZP_oOcxA@mail.gmail.com> <CAFw--DdYkAo79TeZKDFZ5ZdaN4KiLmW2qcceY+cTxuLMdE3QGA@mail.gmail.com>
At 08:58 -0700 on 07 Sep (1347008330), Jeffrey Karrels wrote:
> > Looks like the clang build has bitrotted a little - sorry. It's too
> > late to fix this for 4.2 now but we can sort it out after we branch
> > (i.e. next week) and backport any build fixes for 4.2.1.
> >
>
> No worries. I can try and help out on this. Do you think it is
> worthwhile to start a Wiki page for this type of work.
Yes, I think so. Lars Kurth can sort you out with whatever
accounts/permissions you need.
> I was working with cppcheck, sparse, clang on/for xen...
That all sounds great. I'm in favour of any more analysis we can get,
at least if it doesn't need intrusive annotations.
At 11:43 -0700 on 11 Sep (1347363829), Jeffrey Karrels wrote:
> Just to keep the knowledge in the collective... I updated my clang and
> llvm to the latest trunk:
>
> [builder@xenbuild1 xen-unstable]$ /usr/local/bin/clang -v
> clang version 3.2 (trunk 163631)
> Target: x86_64-unknown-linux-gnu
> Thread model: posix
>
> After that I applied the patch that Tim previously posted and tried
> another make. The xen build succeeded.
Glad to hear it. I'll sort out a better version of that patch
(i.e. that doesn't just remove the code but reimplements it in a
clang-friendly way) tomorrow.
Tim.
next prev parent reply other threads:[~2012-09-12 10:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 22:32 Clang/LLVM version requirements Jeffrey Karrels
2012-09-07 8:50 ` Tim Deegan
2012-09-07 10:04 ` Jan Beulich
2012-09-13 10:11 ` Tim Deegan
2012-09-13 11:52 ` Jan Beulich
2012-09-13 12:21 ` Tim Deegan
2012-09-13 14:01 ` Jan Beulich
2012-09-13 14:55 ` Tim Deegan
2012-09-13 15:05 ` Keir Fraser
2012-09-13 15:09 ` Keir Fraser
2012-09-13 15:27 ` Ian Campbell
2012-09-13 15:51 ` Keir Fraser
2012-09-13 15:22 ` Jan Beulich
2012-09-13 15:34 ` Keir Fraser
2012-09-13 15:06 ` Jan Beulich
2012-09-13 12:40 ` Paolo Bonzini
2012-09-13 14:04 ` Jan Beulich
2012-09-13 14:13 ` Paolo Bonzini
2012-09-13 14:18 ` Jan Beulich
2012-09-07 15:58 ` Jeffrey Karrels
2012-09-11 18:43 ` Jeffrey Karrels
2012-09-12 10:24 ` Stefano Stabellini
2012-09-13 16:15 ` Ian Jackson
2012-09-13 16:41 ` Tim Deegan
2012-09-13 17:04 ` Ian Jackson
2012-09-12 10:31 ` Tim Deegan [this message]
2012-09-12 10:38 ` Ian Campbell
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=20120912103145.GB97347@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=karrelsj@gmail.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).