Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/alpha] Use correct register for FP branches in alpha_next_pc()
Date: Thu, 26 May 2005 15:08:00 -0000	[thread overview]
Message-ID: <20050526063735.GL1530@adacore.com> (raw)

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

Blush... Obvious mistake ... 

I looked at the 18 failures I currently have when running the following
testcase (not yet approved):

        http://sources.redhat.com/ml/gdb-patches/2005-05/msg00546.html

It turns out it was an obvious confusion between the register number
embedded in the instruction, and hte register number as GDB knows it.
Say for instance we have a conditional branch instruction on f16, right
now we read register number 16, which is register a0, not f16! The fix
I just committed seemed to be improving things, but only by chance :-/.
With the attached patch, all tests now PASS.

2005-05-26  Joel Brobecker  <brobecker@adacore.com>

        * alpha-tdep.c (alpha_next_pc): Use correct register number
        for floating-point branch instructions.

Tested on alpha-tru64 5.1a. No regression, fixes all 18 failures
observed in alpha-step.exp.

OK to apply?
-- 
Joel

[-- Attachment #2: alpha-tdep.c.diff --]
[-- Type: text/plain, Size: 1147 bytes --]

Index: alpha-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
retrieving revision 1.149
diff -u -p -r1.149 alpha-tdep.c
--- alpha-tdep.c	20 May 2005 06:56:00 -0000	1.149
+++ alpha-tdep.c	26 May 2005 05:36:41 -0000
@@ -1372,6 +1372,7 @@ alpha_next_pc (CORE_ADDR pc)
 {
   unsigned int insn;
   unsigned int op;
+  int regno;
   int offset;
   LONGEST rav;
   char reg[8];
@@ -1404,7 +1405,19 @@ alpha_next_pc (CORE_ADDR pc)
 	}
 
       /* Need to determine if branch is taken; read RA.  */
-      regcache_cooked_read (current_regcache, (insn >> 21) & 0x1f, reg);
+      regno = (insn >> 21) & 0x1f;
+      switch (op)
+        {
+          case 0x31:              /* FBEQ */
+          case 0x36:              /* FBGE */
+          case 0x37:              /* FBGT */
+          case 0x33:              /* FBLE */
+          case 0x32:              /* FBLT */
+          case 0x35:              /* FBNE */
+            regno += FP0_REGNUM;
+	}
+      
+      regcache_cooked_read (current_regcache, regno, reg);
       rav = extract_signed_integer (reg, 8);
 
       switch (op)

             reply	other threads:[~2005-05-26  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 15:08 Joel Brobecker [this message]
2005-05-28 18:54 ` Daniel Jacobowitz
2005-05-29  2:11   ` 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=20050526063735.GL1530@adacore.com \
    --to=brobecker@adacore.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