From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA 1/3: change PPC E500 raw regcache layout
Date: Fri, 02 Jul 2004 22:26:00 -0000 [thread overview]
Message-ID: <20040702152626.5f36a91a@saguaro> (raw)
In-Reply-To: <vt2r7rxat3d.fsf@zenia.home>
On 30 Jun 2004 11:49:58 -0500
Jim Blandy <jimb@redhat.com> wrote:
> 2004-06-30 Jim Blandy <jimb@redhat.com>
>
> Make the E500 SPE vector registers pseudoregisters, based on raw
> registers for the lower and upper 32-bit gpr halves.
> * ppc-tdep.h (struct gdbarch_tdep): Replace 'ppc_gprs_pseudo_p'
> flag with 'ppc_ev0_upper_regnum'.
> * rs6000-tdep.c: #include "reggroups.h".
> (spe_register_p): The gpr upper-half registers are SPE registers.
> (e500_move_ev_register): New function.
> (e500_pseudo_register_read, e500_pseudo_register_write): Rewitten
> for new raw / pseudo relationship.
> (e500_register_reggroup_p): New function.
> (A4,P8): New regset macro.
> (P): Delete; unused.
> (PPC_EV_REGS, PPC_GPRS_PSEUDO_REGS): Deleted.
> (PPC_SPE_GP_REGS, PPC_SPE_UPPER_GP_REGS, PPC_EV_PSEUDO_REGS): New
> partial regset macros.
> (regiters_e500): Make separate raw registers for the upper and
> lower 32-bit halves of the 64-bit SPE gprs. Make the 'ev' vector
> registers into pseudoregisters.
> (rs6000_gdbarch_init): Initialize the tdep's ppc_ev0_upper_regnum
> members, and adjust initializations of other register numbers.
> Register e500_register_reggroup_p.
> * Makefile.in (rs6000-tdep.o): Update dependencies.
Okay. (Thanks for the explanation preceding the patch.)
Kevin
prev parent reply other threads:[~2004-07-02 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 16:50 Jim Blandy
2004-07-02 22:26 ` 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=20040702152626.5f36a91a@saguaro \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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