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: Fri, 31 Aug 2007 18:15:00 -0000 [thread overview]
Message-ID: <1188584103.4398.4.camel@localhost> (raw)
In-Reply-To: <20070506221707.GA29437@caradoc.them.org>
On Sun, 2007-05-06 at 18:17 -0400, Daniel Jacobowitz wrote:
> On Sun, May 06, 2007 at 11:36:00PM +0200, Ulrich Weigand wrote:
> > Under the circumstances, I'd argue we should just change the built-in
> > type to 128-bit, and make sure that binaries with a DWARF-2 reported
> > "long double" fundamental type of 64-bit still use the proper floating
> > point format info for that type.
> >
> > Anything I'm missing here?
>
> Sounds reasonable to me.
Bringing back the topic. The patch is handling those types as 128-bit in
length by default. Depending on the dwarf info, gdb switches to either
64-bit or 128-bit during printing.
Isn't it right? Maybe i'm missing something regarding GDB's built-in
types for long doubles.
Regards,
--
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com
next prev parent reply other threads:[~2007-08-31 18:15 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
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 [this message]
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=1188584103.4398.4.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