This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: question regarding gnu-isms

To: Aron Griffis <aron@xxxxxx>
Subject: [Xen-devel] Re: question regarding gnu-isms
From: Andi Kleen <ak@xxxxxxx>
Date: 28 Apr 2006 07:09:36 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 27 Apr 2006 22:09:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060427223641.GG3572@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060427223641.GG3572@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Aron Griffis <aron@xxxxxx> writes:

> I understand most of the gcc extensions that I find in xen, for
> example ({...}) in a #define.  However I've come across a couple that
> I'm not familiar with.  Does somebody mind explaining the point of
> these?
> from linux-2.6-xen-sparse/include/asm-ia64/hypervisor.h:
>     #define __pte_ma(_x)    ((pte_t) {(_x)})

This isn't a GNUism anymore, it's C99.


Xen-devel mailing list