From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>,
Kevin Buettner <kevinb@redhat.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Another patch to aix-thread.c
Date: Mon, 22 Jul 2002 15:52:00 -0000 [thread overview]
Message-ID: <1020722223002.ZM26189@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@ges.redhat.com> "Re: Another patch to aix-thread.c" (Jul 22, 3:43pm)
On Jul 22, 3:43pm, Andrew Cagney wrote:
> > + regcache_collect (regno, iar);
> > + regcache_collect (regno + 1, msr);
>
> Suggest ``regno + 0''. Otherwize gdb_indent.sh will mess up your nice
> alignment.
I agree that this is a good idea. However, I'm about to make some
changes which will obviate the use of regno + N. I.e, I'm about to
transform the above into the following:
struct gdbarch_tdep *tdep = gdbarch_tdep (current_gdbarch);
...
regcache_collect (PC_REGNUM, iar);
regcache_collect (tdep->ppc_ps_regnum, msr);
...
This will also eliminate the use of FIRST_UISA_SP_REGNUM from the
file. While I'm at it, I'll also look at eliminating this macro
from rs6000-nat.c which means that it can be eliminated from GDB
entirely.
(It bothered me that aix-thread.c was making assumptions about the
order of the registers. Also, it was more difficult to verify the
correctness by having expressions of the form "regno + small_offset".
I was having to look elsewhere to verify that the specified offset
was correct.)
Kevin
prev parent reply other threads:[~2002-07-22 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 13:09 Michael Snyder
2002-07-22 12:41 ` Kevin Buettner
2002-07-22 13:11 ` Andrew Cagney
2002-07-22 15:52 ` Kevin Buettner [this message]
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=1020722223002.ZM26189@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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