From: Elena Zannoni <ezannoni@cygnus.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc: include register numbers in gdbarch_tdep structure.
Date: Sun, 09 Dec 2001 13:38:00 -0000 [thread overview]
Message-ID: <15379.56127.235381.439351@krustylu.cygnus.com> (raw)
In-Reply-To: <1011209212323.ZM18906@ocotillo.lan>
Kevin Buettner writes:
> On Dec 9, 3:04pm, Elena Zannoni wrote:
>
> > This is a new patch for
> >
> > http://sources.redhat.com/ml/gdb-patches/2001-12/msg00160.html
> >
> > Tested on aix4.3, solaris-x-powerpc-eabi, ppcnbsd, ppclinux.
> >
> > Elena
> >
> > 2001-12-09 Elena Zannoni <ezannoni@redhat.com>
> >
> > * config/rs6000/tm-rs6000.h (STAB_REG_TO_REGNUM): Remove
> > definition, it is now multiarched.
> > * ppc-tdep.h (struct gdbarch_tdep): Move from rs6000-tdep.c. Add
> > fields for special register numbers.
> > * rs6000-tdep.c (rs6000_gdbarch_init): Initialize new tdep special
> > regnum fields.
> > (rs6000_saved_pc_after_call): Use gdbarch_tdep registers fields
> > instead of hardcoded macros.
> > (branch_dest, rs6000_pop_frame, rs6000_fix_call_dummy,
> > ppc_push_return_address, rs6000_frame_saved_pc,
> > frame_get_saved_regs, rs6000_frame_chain,
> > rs6000_store_return_value): Ditto.
> > (rs6000_stab_reg_to_regnum): New function.
> > * ppcnbsd-nat.c (fetch_inferior_registers,
> > store_inferior_registers, fetch_core_registers): Ditto.
> > * ppc-linux-tdep.c (ppc_linux_in_sigtramp,
> > ppc_linux_frame_init_saved_regs): Ditto.
> > * ppc-linux-nat.c (ppc_register_u_addr, supply_gregset,
> > fill_gregset): Ditto.
> > * ppc-bdm.c (bdm_ppc_fetch_registers, bdm_ppc_store_registers):
> > Ditto.
>
> Approved.
>
> Though I do wonder if it was really necessary to move register
> numbers which are truly constant to the gdbarch_tdep struct. BTW,
> this wouldn't bother me so much if we could use inline functions
> in C.
>
> Kevin
Thanks Kevin!
Committed.
The reason for moving the regnums to the tdep structure is that they
are all in one place. It seems cleaner to have defintions like these
be localized. I also found that in case of another processor, newer
revisions moved the regs around a bit, so I had to multiarch them
anyway. It seems like the ppc is a bit more stable in this regard
though.
Elena
next prev parent reply other threads:[~2001-12-09 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 11:58 Elena Zannoni
2001-12-09 13:24 ` Kevin Buettner
2001-12-09 13:38 ` Elena Zannoni [this message]
2001-12-09 15:09 ` Andrew Cagney
2001-12-12 12:16 ` Mark Kettenis
2001-12-10 11:33 ` Michael Snyder
2001-12-10 12:25 ` Kevin Buettner
2001-12-10 12:41 ` Elena Zannoni
2001-12-10 13:22 ` Kevin Buettner
2001-12-10 14:34 ` Andrew Cagney
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=15379.56127.235381.439351@krustylu.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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