From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Printing decimal128 types out of registers
Date: Thu, 17 Jan 2008 19:36:00 -0000 [thread overview]
Message-ID: <1200598580.32125.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1200596592.27321.20.camel@gargoyle>
On Thu, 2008-01-17 at 17:03 -0200, Luis Machado wrote:
> Hi,
>
> The patch to handle DFP expressions had some overlapping with this
> patch, and since this was a bit old already, follows a refreshed version
> for HEAD.
>
> The patch remains essentially the same, with a few fixes. Running the
> testsuite showed no regressions on 32-bit/64-bit ppc.
>
> Is this OK to go in?
A few comments, mostly formatting:
> + /* These are the e500 pseudo-registers. */
> + if (tdep->ppc_ev0_regnum >= 0
> + && regnum >= tdep->ppc_ev0_regnum
> + && regnum < tdep->ppc_ev0_regnum + 32)
> + return rs6000_builtin_type_vec64 (gdbarch);
> +
> + /* These are the ppc decimal128 pseudo-registers. */
> + if (tdep->ppc_dl0_regnum >= 0
> + && regnum >= tdep->ppc_dl0_regnum
> + && regnum < tdep->ppc_dl0_regnum + 16)
> + return builtin_type (current_gdbarch)->builtin_declong;;
>
> + /* These are the e500 pseudo-registers. */
> + if (tdep->ppc_ev0_regnum < 0
> + && regnum < tdep->ppc_ev0_regnum
> + && regnum >= tdep->ppc_ev0_regnum + 32)
> + return -1;
> +
> + /* These are the ppc decimal128 pseudo-registers. */
> + if (tdep->ppc_dl0_regnum < 0
> + && regnum < tdep->ppc_dl0_regnum
> + && regnum >= tdep->ppc_dl0_regnum + 16)
> + return -1;
The return statements above are too indented.
> - int have_fpu = 1, have_spe = 0, have_mq = 0, have_altivec = 0;
> + int have_fpu = 1, have_spe = 0, have_mq = 0, have_altivec = 0,
> + have_dfp128 = 0;
have_dfp128 shouldn't be aligned with int. Not sure which column it
should be though.
> + else
> + if (have_dfp128)
> + {
> + set_gdbarch_pseudo_register_read (gdbarch,
ppc_pseudo_register_read);
> + set_gdbarch_pseudo_register_write (gdbarch,
ppc_pseudo_register_write);
> + }
>
> +
> + if (have_spe)
> + set_gdbarch_num_pseudo_regs (gdbarch, 32);
> + else
> + if (have_dfp128)
> + set_gdbarch_num_pseudo_regs (gdbarch, 16);
IMHO, "else" should be immediately followed by if, not put in a
separate line.
> Index: gdb/features/rs6000/powerpc-64.c
> [...]
> Index: gdb/features/rs6000/powerpc-32.c
These files are generated. You should edit the XML and regenerate.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-01-17 19:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 19:33 [PATCH] PPC - Printing Decimal 128 " Luis Machado
2007-11-26 21:40 ` Luis Machado
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 [this message]
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=1200598580.32125.11.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.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