From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2368 invoked by alias); 29 Sep 2008 17:00:14 -0000 Received: (qmail 2254 invoked by uid 22791); 29 Sep 2008 17:00:13 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 29 Sep 2008 16:59:33 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 5B1C510D24; Mon, 29 Sep 2008 16:59:31 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 245BA1019C; Mon, 29 Sep 2008 16:59:31 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KkM5q-0005wc-Bg; Mon, 29 Sep 2008 12:59:30 -0400 Date: Mon, 29 Sep 2008 17:00:00 -0000 From: Daniel Jacobowitz To: Thiago Jung Bauermann Cc: Eli Zaretskii , gdb-patches@sources.redhat.com Subject: Re: [rfc] expose gdb values to python Message-ID: <20080929165930.GA19283@caradoc.them.org> Mail-Followup-To: Thiago Jung Bauermann , Eli Zaretskii , gdb-patches@sources.redhat.com References: <1221199426.24580.26.camel@localhost.localdomain> <20080921042657.GB29631@caradoc.them.org> <20080925114659.GA30878@caradoc.them.org> <1222704906.8567.45.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1222704906.8567.45.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00557.txt.bz2 On Mon, Sep 29, 2008 at 01:15:05PM -0300, Thiago Jung Bauermann wrote: > +/* Python's float type corresponds to native C's double type (which is > + assumed to use IEEE double format). */ > +#define builtin_type_pyfloat builtin_type_ieee_double > + > +/* Python's long type corresponds to native C's long long type (which is > + assumed to be int64_t). */ > +#define builtin_type_pylong builtin_type_int64 > + > +/* The current language may not have a boolean type, so always use an > + integer as boolean type. Hopefully any language can deal with integers > + as boolean values. */ > +#define builtin_type_pybool builtin_type_int32 Can't you get an architecture to use when you need these? I'm scared the double change, in particular, will break any non-ieee target. This is supposed to be target arithmetic, we should use the target formats. -- Daniel Jacobowitz CodeSourcery