Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: put fpscr in right place in core file
Date: Wed, 24 Mar 2004 16:17:00 -0000	[thread overview]
Message-ID: <vt28yhqxlqs.fsf@zenia.home> (raw)


This fixes a failure in gcore.exp.

2004-02-29  Jim Blandy  <jimb@redhat.com>

	* ppc-linux-nat.c (fill_fpregset): Place the 32-bit value of the
	fpscr in the right end of the 64-bit slot for it in the fpregset
	array.

Index: gdb/ppc-linux-nat.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/ppc-linux-nat.c,v
retrieving revision 2.19.6.4
diff -c -r2.19.6.4 ppc-linux-nat.c
*** gdb/ppc-linux-nat.c	29 Feb 2004 07:51:24 -0000	2.19.6.4
--- gdb/ppc-linux-nat.c	1 Mar 2004 04:51:15 -0000
***************
*** 1032,1038 ****
  	regcache_collect (FP0_REGNUM + regi, (char *) (*fpregsetp + regi));
      }
    if ((regno == -1) || regno == tdep->ppc_fpscr_regnum)
!     regcache_collect (tdep->ppc_fpscr_regnum, (char *) (*fpregsetp + regi));
  }
  
  
--- 1032,1044 ----
  	regcache_collect (FP0_REGNUM + regi, (char *) (*fpregsetp + regi));
      }
    if ((regno == -1) || regno == tdep->ppc_fpscr_regnum)
!     {
!       /* The FPSCR is stored in the low order word of the last
!          doubleword in the fpregset.  */
!       int offset = (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG) ? 4 : 0;
!       regcache_collect (tdep->ppc_fpscr_regnum,
!                         (char *) (*fpregsetp + regi) + offset);
!     }
  }
  
  


             reply	other threads:[~2004-03-24 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 16:17 Jim Blandy [this message]
2004-03-26 14:12 ` Kevin Buettner
2004-03-26 20:29   ` Jim Blandy

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=vt28yhqxlqs.fsf@zenia.home \
    --to=jimb@redhat.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