Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Greg Page <gpage@ind.alcatel.com>
To: gdb-patches@sources.redhat.com
Subject: Patch for GDB rs6000-tdep.c
Date: Wed, 17 May 2006 18:13:00 -0000	[thread overview]
Message-ID: <446B64BA.8050905@ind.alcatel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

The attached is a patch for the file gdb-6.4/gdb/rs6000-tdep.c.

The problem: The register definitions for the e500 assume only 4 bytes 
per floating-point register but the gdbserver assumes 8 bytes per 
floating-point register.

Changelog
rs6000-tdep.c (registers_e500[]): Use COMMON_UISA_REGS to define general 
purpose, floating-point, pc, and ps registers.


[-- Attachment #2: e500.patch --]
[-- Type: text/x-patch, Size: 802 bytes --]

*** rs6000-tdep.c	2005-11-01 12:32:36.000000000 -0700
--- rs6000-tdep.c.new	2006-05-17 11:28:45.526751000 -0600
*************** static const struct reg registers_7400[]
*** 2629,2637 ****
  /* Motorola e500.  */
  static const struct reg registers_e500[] =
  {
!   /*   0 ..  31 */ PPC_SPE_GP_REGS,
!   /*  32 ..  63 */ PPC_SPE_UPPER_GP_REGS,
!   /*  64 ..  65 */ R(pc), R(ps),
    /*  66 ..  70 */ PPC_UISA_NOFP_SPRS,
    /*  71 ..  72 */ R8(acc), S4(spefscr),
    /* NOTE: Add new registers here the end of the raw register
--- 2629,2635 ----
  /* Motorola e500.  */
  static const struct reg registers_e500[] =
  {
!   /* 0 .. 65 */ COMMON_UISA_REGS,
    /*  66 ..  70 */ PPC_UISA_NOFP_SPRS,
    /*  71 ..  72 */ R8(acc), S4(spefscr),
    /* NOTE: Add new registers here the end of the raw register

             reply	other threads:[~2006-05-17 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 18:13 Greg Page [this message]
2006-05-17 19:03 ` Daniel Jacobowitz
     [not found]   ` <446B72FE.1070505@ind.alcatel.com>
2006-05-17 19:07     ` Daniel Jacobowitz

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=446B64BA.8050905@ind.alcatel.com \
    --to=gpage@ind.alcatel.com \
    --cc=gdb-patches@sources.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