From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <ak@suse.de>
Subject: Re: question regarding gnu-isms
Date: 28 Apr 2006 07:09:36 +0200
Message-ID: <p73r73i70bz.fsf@bragg.suse.de>
References: <20060427223641.GG3572@vino.zko.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20060427223641.GG3572@vino.zko.hp.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: Aron Griffis <aron@hp.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Aron Griffis <aron@hp.com> 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.

-Andi