From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC] Detecting and printing 128-bit long double values for PPC
Date: Mon, 30 Apr 2007 13:19:00 -0000 [thread overview]
Message-ID: <20070430131616.GB25539@caradoc.them.org> (raw)
In-Reply-To: <1177938530.15264.9.camel@localhost>
On Mon, Apr 30, 2007 at 10:08:48AM -0300, Luis Machado wrote:
> Isn't the length of the data type supposed to be available from DWARF?
> Or this should still be included by the binaries that actually generate
> the DWARF info?
This is "the ABI-defined long double type", which GDB distinguishes
from "the debug info describing long double". I suppose you could
come up with a way to distinguish binaries based on what their debug
info has to say about it, if it mentions long double anywhere.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-30 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 14:08 Luis Machado
2007-04-28 16:19 ` Daniel Jacobowitz
2007-04-28 16:27 ` Ulrich Weigand
2007-04-28 16:49 ` Daniel Jacobowitz
2007-04-28 23:47 ` Luis Machado
2007-04-30 12:28 ` Ulrich Weigand
2007-04-30 12:41 ` Daniel Jacobowitz
2007-04-30 13:15 ` Luis Machado
2007-04-30 13:19 ` Daniel Jacobowitz [this message]
2007-04-30 13:51 ` Luis Machado
2007-04-30 13:53 ` Luis Machado
2007-04-30 14:12 ` Daniel Jacobowitz
2007-05-06 21:36 ` Ulrich Weigand
2007-05-06 22:17 ` Daniel Jacobowitz
2007-08-31 18:15 ` Luis Machado
2007-08-31 18:27 ` Joseph S. Myers
2007-04-30 18:03 ` Luis Machado
2007-04-30 13:08 ` Luis Machado
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=20070430131616.GB25539@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=uweigand@de.ibm.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