From: Patrick Welche <prlw1@cam.ac.uk>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xen.org
Subject: clang compilation
Date: Fri, 16 Aug 2013 08:17:51 +0100 [thread overview]
Message-ID: <20130816071751.GE363@quark> (raw)
In-Reply-To: <20130815211531.GA67757@ocelot.phlegethon.org>
On Thu, Aug 15, 2013 at 10:15:31PM +0100, Tim Deegan wrote:
> > > I've tested with every GCC I can lay my hands on (and clang 3.0),
> > > building x86 and ARM.
Joerg has a "clang fix" for warnings for xen/arch/x86/time.c, essentially
mul to mull or mulq - did you see such warnings when testing with clang?
http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/sysutils/xenkernel42/patches/patch-xen_arch_x86_time.c
Cheers,
Patrick
next prev parent reply other threads:[~2013-08-16 7:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 13:25 [PATCH 0/3] stdinc-related build fixes Tim Deegan
2013-08-15 13:25 ` [PATCH 1/3] xen: move some arch CFLAGS into the common Rules.mk Tim Deegan
2013-08-15 14:11 ` Ian Campbell
2013-08-15 13:25 ` [PATCH 2/3] xen: move -nostdinc into " Tim Deegan
2013-08-15 14:12 ` Ian Campbell
2013-08-15 13:25 ` [PATCH 3/3] xen: Add stdbool.h workaround for BSD Tim Deegan
2013-08-15 14:15 ` Ian Campbell
2013-08-19 13:48 ` Ian Jackson
2013-08-19 14:16 ` Tim Deegan
2013-08-19 16:48 ` Ian Jackson
2013-08-15 13:51 ` [PATCH 0/3] stdinc-related build fixes Jan Beulich
2013-08-15 15:26 ` Keir Fraser
2013-08-15 15:55 ` Solaris / FreeBSD builds (was Re: [PATCH 0/3] stdinc-related build fixes.) Tim Deegan
2013-08-15 19:49 ` [PATCH 0/3] stdinc-related build fixes Patrick Welche
2013-08-15 19:58 ` Andrew Cooper
2013-08-15 21:05 ` Patrick Welche
2013-08-15 21:15 ` Tim Deegan
2013-08-16 7:17 ` Patrick Welche [this message]
2013-08-16 8:17 ` clang compilation Tim Deegan
2013-08-16 8:48 ` Jan Beulich
2013-08-16 8:54 ` Tim Deegan
2013-08-16 9:27 ` Jan Beulich
2013-08-16 10:00 ` Jan Beulich
2013-08-16 8:23 ` [PATCH 0/3] stdinc-related build fixes Jan Beulich
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=20130816071751.GE363@quark \
--to=prlw1@cam.ac.uk \
--cc=tim@xen.org \
--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).