WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] question regarding gnu-isms

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] question regarding gnu-isms
From: Aron Griffis <aron@xxxxxx>
Date: Thu, 27 Apr 2006 18:36:41 -0400
Delivery-date: Thu, 27 Apr 2006 15:37:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
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)})

    What's the point of the braces here?

same file:

    #define xen_create_contiguous_region(vstart, order, address_bits) ({0;})

    This looks like the usual ({...}) construction but seems
    pointless.  The nearest explanation I could gather for this
    applies only to C++...  surely I'm missing something. :-)

Thanks,
Aron

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel