From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tim Deegan <tim@xen.org>
Subject: Re: [PATCH 01/34] xen: clang: Disable
 initializer-overrides warning
Date: Wed, 26 Mar 2014 16:09:59 +0100
Message-ID: <20140326150959.GA29150@deinos.phlegethon.org>
References: <1395766541-23979-1-git-send-email-julien.grall@linaro.org>
	<1395766541-23979-2-git-send-email-julien.grall@linaro.org>
	<5332CD4B020000780000247A@nat28.tlf.novell.com>
	<5332EB9E.6050409@linaro.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72) (envelope-from <tim@xen.org>)
	id 1WSpSt-0006om-EI
	for xen-devel@lists.xenproject.org; Wed, 26 Mar 2014 15:10:03 +0000
Content-Disposition: inline
In-Reply-To: <5332EB9E.6050409@linaro.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com, Keir Fraser <keir@xen.org>, ian.campbell@citrix.com, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

At 15:00 +0000 on 26 Mar (1395842446), Julien Grall wrote:
> Hi Jan,
> 
> On 03/26/2014 11:51 AM, Jan Beulich wrote:
> >>>> On 25.03.14 at 17:55, <julien.grall@linaro.org> wrote:
> >> --- a/xen/Rules.mk
> >> +++ b/xen/Rules.mk
> >> @@ -68,6 +68,8 @@ ifneq ($(max_phys_irqs),)
> >>  CFLAGS-y                += -DMAX_PHYS_IRQS=$(max_phys_irqs)
> >>  endif
> >>  
> >> +CFLAGS-$(clang)         += -Wno-initializer-overrides
> > 
> > And this is supported by all clang versions we permit to be used, i.e.
> > doesn't need to be done conditionally?
> 
> I've tried to compile with clang 3.0-3.5 (used by Debian wheezy).
> 
> In another dimension can we really say we are supporting clang when most
> of the time it's not possible to compile Xen with it? For instance,
> building Xen 4.4 with Clang doesn't work.
> I think we might need to have a build test for clang.

Most of the breakage seems to come with newer versions of clang,
rather than newer versions of Xen.  Still, a clang build test would be
a good idea.

Cheers,

Tim.