Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH] MIPS/Linux: Update the number of pseudo registers too
Date: Tue, 06 Dec 2011 22:26:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1112062118470.6710@tp.orcam.me.uk> (raw)

Hi,

 Similarly to the previous general MIPS change (pc_regnum and sp_regnum) 
the Linux backend needs to update the number of pseudo registers as it 
adds the "restart" register.  No regressions in mips-linux-gnu testing 
(native and remote).  OK to apply?

2011-12-06  Maciej W. Rozycki  <macro@codesourcery.com>

	gdb/
	* mips-linux-tdep.c (mips_linux_init_abi): Set num_pseudo_regs
	too.

  Maciej

gdb-mips-num-pseudo-regs.diff
Index: gdb-fsf-trunk-quilt/gdb/mips-linux-tdep.c
===================================================================
--- gdb-fsf-trunk-quilt.orig/gdb/mips-linux-tdep.c	2011-11-24 00:54:31.955605130 +0000
+++ gdb-fsf-trunk-quilt/gdb/mips-linux-tdep.c	2011-11-24 00:55:54.545604049 +0000
@@ -1325,6 +1325,7 @@ mips_linux_init_abi (struct gdbarch_info
 	 described or not).  */
       gdb_assert (gdbarch_num_regs (gdbarch) <= MIPS_RESTART_REGNUM);
       set_gdbarch_num_regs (gdbarch, MIPS_RESTART_REGNUM + 1);
+      set_gdbarch_num_pseudo_regs (gdbarch, MIPS_RESTART_REGNUM + 1);
 
       /* If it's present, then assign it to the reserved number.  */
       feature = tdesc_find_feature (info.target_desc,


             reply	other threads:[~2011-12-06 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 22:26 Maciej W. Rozycki [this message]
2011-12-08  8:37 ` Joel Brobecker
2011-12-08  9:04   ` Mark Kettenis
2011-12-08  9:26     ` Joel Brobecker
2011-12-08 12:36       ` Mark Kettenis
2012-02-27 21:37         ` Maciej W. Rozycki
2011-12-08 13:49 ` Joel Brobecker

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=alpine.DEB.1.10.1112062118470.6710@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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