From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] PPC - Printing Decimal 128 types out of registers
Date: Mon, 26 Nov 2007 21:40:00 -0000 [thread overview]
Message-ID: <1196113213.4302.7.camel@localhost> (raw)
In-Reply-To: <1194460412.6686.34.camel@localhost>
Hi there,
Did anyone have a chance to go through this one?
Regards,
Luis
On Wed, 2007-11-07 at 16:33 -0200, Luis Machado wrote:
> Hi folks,
>
> I'm continuing the work to enhance DFP type support on GDB. DFP types
> are nativelly supported on the Power6 processor, thus they are stored in
> registers as so. This patch handles the printing and setting of
> Decimal128 types directly out of/in the registers.
>
> A Decimal128 type is stored using pairs of Floating Point registers, and
> it always starts in an even-numbered register. So, we could, for
> example, have a Decimal128 var taking up FPR0-FPR1, FPR10-FPR11, but
> never FPR1-FPR2 or FPR23-24.
>
> Right now GDB isn't able to print those vars as it doesn't know they
> take up more than one register.
>
> The idea to overcome this was to create a new set of 16 Decimal128-typed
> pseudo-registers called DL (Standing for "D"ecimal "L"ong Double) that
> would represent all 16 pairs of Floating Point Registers.. By using a
> pseudo-register mechanism, we're able to force the DL/FPR registers to
> map directly into the FPR/DL registers.
>
> Benefits of this change include:
>
> * Better printing support for Decimal128 types. We just print the
> register as is. No need to include casting tricks and arrays to print
> that value.
>
> * Straightforward way of setting Decimal128 values directly in the
> registers. We just "set $dl0=1.23dl", for example, and it's
> automatically set.
>
> * Overview of the state of 16 Decimal128 registers using the "info reg
> all" command.
>
>
> Supporting the patch there is also a number of other modifications, as
> listed:
>
> * DFP types are now global since they were included as predefined types
> in the "target-descriptions.c" file.
>
> * A simple testcase making sure the registers are working as expected.
>
> * Piece of documentation for the GDB manual.
>
> * Fix to display a 128-bit hex literal representation of Decimal128
> types (using "info reg").
>
> Also note that this support will be available for both ppc64 and ppc32.
>
> Looking forward to have comments and suggestions for improvements.
>
> Regards,
> Luis
--
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com
next prev parent reply other threads:[~2007-11-26 21:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 19:33 Luis Machado
2007-11-26 21:40 ` Luis Machado [this message]
2007-12-26 12:42 ` [PING] " Luis Machado
2008-01-17 19:03 ` Printing decimal128 " Luis Machado
2008-01-17 19:36 ` Thiago Jung Bauermann
2008-01-18 15:43 ` Luis Machado
2008-01-18 16:12 ` Mark Kettenis
2008-01-18 16:38 ` Luis Machado
2008-01-18 17:20 ` Mark Kettenis
2008-01-18 18:52 ` Luis Machado
2008-01-18 19:54 ` Mark Kettenis
2008-01-19 0:04 ` Daniel Jacobowitz
2008-01-21 14:55 ` Thiago Jung Bauermann
2008-01-21 17:31 ` Mark Kettenis
2008-01-23 15:39 ` Thiago Jung Bauermann
2008-01-21 17:54 ` Daniel Jacobowitz
2008-01-23 15:11 ` Thiago Jung Bauermann
2008-01-23 15:20 ` Daniel Jacobowitz
2008-01-23 16:56 ` Thiago Jung Bauermann
2008-01-30 15:46 ` Thiago Jung Bauermann
2008-01-30 16:45 ` Thiago Jung Bauermann
2008-01-30 18:27 ` Mark Kettenis
2008-01-30 18:38 ` Thiago Jung Bauermann
2008-01-30 20:28 ` Mark Kettenis
2008-01-30 21:26 ` Thiago Jung Bauermann
2008-01-30 21:39 ` Ulrich Weigand
2008-01-31 14:47 ` Thiago Jung Bauermann
2008-01-31 15:06 ` Ulrich Weigand
2008-01-30 21:42 ` Mark Kettenis
2008-01-30 23:03 ` Eli Zaretskii
2008-01-31 15:44 ` Thiago Jung Bauermann
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=1196113213.4302.7.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/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