From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [rfc] expose gdb values to python
Date: Mon, 29 Sep 2008 17:00:00 -0000 [thread overview]
Message-ID: <20080929165930.GA19283@caradoc.them.org> (raw)
In-Reply-To: <1222704906.8567.45.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2008-09-29 17:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 6:05 Thiago Jung Bauermann
2008-09-20 21:29 ` Tom Tromey
2008-09-21 4:27 ` Daniel Jacobowitz
2008-09-25 4:33 ` Thiago Jung Bauermann
2008-09-25 11:47 ` Daniel Jacobowitz
2008-09-26 2:00 ` Thiago Jung Bauermann
2008-09-26 9:30 ` Eli Zaretskii
2008-09-28 1:19 ` Thiago Jung Bauermann
2008-09-28 18:19 ` Eli Zaretskii
2008-09-29 16:16 ` Thiago Jung Bauermann
2008-09-29 17:00 ` Daniel Jacobowitz [this message]
2008-09-30 4:07 ` Thiago Jung Bauermann
2008-09-30 12:41 ` Daniel Jacobowitz
2008-10-01 3:18 ` Thiago Jung Bauermann
2008-10-01 11:40 ` Daniel Jacobowitz
2008-09-29 18:52 ` Eli Zaretskii
2008-09-26 20:57 ` Daniel Jacobowitz
2008-10-01 5:39 ` Joel Brobecker
2008-10-04 22:14 ` Thiago Jung Bauermann
2008-09-25 4:49 ` Thiago Jung Bauermann
2008-09-26 23:08 ` Tom Tromey
2008-10-01 5:48 ` Joel Brobecker
2008-10-01 15:12 ` Tom Tromey
2008-10-01 16:04 ` Joel Brobecker
2008-10-04 22:21 ` Daniel Jacobowitz
2008-10-05 0:00 ` Tom Tromey
2008-10-06 18:49 ` Joel Brobecker
2008-10-06 21:15 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080929165930.GA19283@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox