From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
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:15:00 -0000 [thread overview]
Message-ID: <1177938530.15264.9.camel@localhost> (raw)
In-Reply-To: <20070430123432.GA30827@caradoc.them.org>
> GDB will always read 16 bytes when it uses its built in notion of
> "long double". But if it gets the type from DWARF info, then it will
> be an eight byte floating point type, and I bet GDB is automatically
> handling it as a double.
>
> That means that the patch is still incorrect, but the consequences of
> getting this wrong are not the immediately obvious ones. I don't know
> if saying (long double) in the command line is going to use the type
> from debug info or from the gdbarch; our handling of base types has
> always confused me somewhat.
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?
Regards,
Luis
next prev parent reply other threads:[~2007-04-30 13:08 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 [this message]
2007-04-30 13:19 ` Daniel Jacobowitz
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=1177938530.15264.9.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--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