Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: gdb-patches@sourceware.org
Cc: Nigel Stephens <nigel@mips.com>,
	     "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: remote-mips.c: Build fix
Date: Wed, 12 Dec 2007 16:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0712121621510.29890@perivale.mips.com> (raw)

Hello,

 The deprecated_register_valid[] array has been removed and 
regcache_set_valid_p() has to be used instead.  Following is a fix that 
makes remote-mips.c build again.

2007-12-12  Nigel Stephens  <nigel@mips.com>

	* remote-mips.c (mips_load): Use regcache_set_valid_p() instead
	of setting deprecated_register_valid array directly.

 OK to apply?

  Maciej

14440-5.diff
Index: binutils-quilt/src/gdb/remote-mips.c
===================================================================
--- binutils-quilt.orig/src/gdb/remote-mips.c	2007-12-12 16:08:14.000000000 +0000
+++ binutils-quilt/src/gdb/remote-mips.c	2007-12-12 16:08:26.000000000 +0000
@@ -3274,7 +3274,8 @@
       /* Work around problem where PMON monitor updates the PC after a load
          to a different value than GDB thinks it has. The following ensures
          that the write_pc() WILL update the PC value: */
-      deprecated_register_valid[gdbarch_pc_regnum (current_gdbarch)] = 0;
+      regcache_set_valid_p (get_current_regcache (),
+			    gdbarch_pc_regnum (current_gdbarch), 0);
     }
   if (exec_bfd)
     write_pc (bfd_get_start_address (exec_bfd));


             reply	other threads:[~2007-12-12 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 16:34 Maciej W. Rozycki [this message]
2007-12-12 18:36 ` 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=Pine.LNX.4.61.0712121621510.29890@perivale.mips.com \
    --to=macro@mips.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=nigel@mips.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