From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] unnamed union structure members are
	dangerous to expose in public headers
Date: Tue, 25 Mar 2008 17:33:53 +0000
Message-ID: <C40EE801.1E514%keir.fraser@eu.citrix.com>
References: <20080325172534.GD6845@implementation.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20080325172534.GD6845@implementation.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Samuel Thibault <samuel.thibault@eu.citrix.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 25/3/08 17:25, "Samuel Thibault" <samuel.thibault@eu.citrix.com> wrote:

> will return 0x13e0 when compiled without gcc -std=c99, while the
> expected value is 0x1430, resulting to seg faults and all kinds of
> tricks.  Compiling with
> 
> #include "/usr/include/xen/foreign/x86_64.h"
> 
> shows why:
> 
> /usr/include/xen/foreign/x86_64.h:88: warning: declaration does not
> declare anything

This raises two obvious questions:
 1. Why building with -std=c99?
 2. Why building without -Werror?

 -- Keir