This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Detecting and printing 128-bit long double values for PPC
- From: Luis Machado <luisgpm at linux dot vnet dot ibm dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, gdb-patches ml <gdb-patches at sourceware dot org>
- Date: Fri, 31 Aug 2007 15:15:02 -0300
- Subject: Re: [RFC] Detecting and printing 128-bit long double values for PPC
- References: <20070430135259.GA7430@caradoc.them.org> <200705062136.l46La00Q029476@d12av02.megacenter.de.ibm.com> <20070506221707.GA29437@caradoc.them.org>
- Reply-to: luisgpm at linux dot vnet dot ibm dot com
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