From: Joel Brobecker <brobecker@adacore.com>
To: Chris January <chris.january@allinea.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] AIX: Add another way of setting up the frame pointer to skip_prologue
Date: Fri, 09 Mar 2012 19:48:00 -0000 [thread overview]
Message-ID: <20120309194834.GG2853@adacore.com> (raw)
In-Reply-To: <1331217602.2742.14.camel@gumtree>
Chris,
> Add support for compilers that use the oril r29, r1, 0x0 instruction to
> set up the frame pointer.
>
> 2012-03-08 Chris January <chris.january@allinea.com>
>
> * rs6000-tdep.c (skip_prologue): Support the oril r29, r1, 0x0
> instruction.
Same comments as before: Looks good, but has it been validated against
the testsuite?
I am just going to suggest one tiny change, which is a bit of a nitpick,
but I think makes the code relatively consistent:
> ---
> diff --git a/gdb/rs6000-tdep.c b/gdb/rs6000-tdep.c
> index a8ff777..9d4fd40 100644
> --- a/gdb/rs6000-tdep.c
> +++ b/gdb/rs6000-tdep.c
> @@ -1822,6 +1822,15 @@ skip_prologue (struct gdbarch *gdbarch, CORE_ADDR
> pc, CORE_ADDR lim_pc,
>
> /* Set up frame pointer */
> }
> + else if (op == 0x603d0000 /* oril r29, r1, 0x0 */)
I would put the comment outside of the closing parens. I know we do
this for multi-line conditions, but this one fits in a single line,
so we can put it outside, and that way, it doesn't look like a parens
is missing.
> + {
> + fdata->frameless = 0;
> + framep = 1;
> + fdata->alloca_reg = (tdep->ppc_gp0_regnum + 29);
> + continue;
> +
> + /* Another way to set up the frame pointer. */
> + }
> else if (op == 0x603f0000 /* oril r31, r1, 0x0 */
> || op == 0x7c3f0b78)
> { /* mr r31, r1 */
>
--
Joel
next prev parent reply other threads:[~2012-03-09 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 14:40 Chris January
2012-03-09 19:48 ` Joel Brobecker [this message]
2012-03-12 13:14 ` Chris January
2012-03-12 13:43 ` Mark Kettenis
2012-03-13 15:18 ` Chris January
2012-03-13 16:50 ` Joel Brobecker
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=20120309194834.GG2853@adacore.com \
--to=brobecker@adacore.com \
--cc=chris.january@allinea.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