From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/alpha] Add handling of FP control insn in software-single step (second try)
Date: Fri, 20 May 2005 02:34:00 -0000 [thread overview]
Message-ID: <20050520012055.GY1462@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
This is a rework of:
http://sources.redhat.com/ml/gdb-patches/2005-05/msg00405.html
Hopefully this patch will be more acceptable.
2005-05-17 Joel Brobecker <brobecker@adacore.com>
* alpha-tdep.c (fp_register_zero_p): New function.
(fp_register_sign_bit): New function.
(alpha_next_pc): Add support for floating-point control instructions.
Tested on alpha-tru64 5.1a with no regression. I'll try to contribute
an asm test asap.
One remark: For zero_mask in fp_register_zero_p(), Richard suggested
to use "((LONGEST) 1 << 63) - 1", but that triggered an overflow warning
from GCC. So I reverted to using the xor binary operator. Daniel said
that many things would break in GDB with 128-bit types, so I think the
xor is quite acceptable for now.
OK to commit?
Thanks,
--
Joel
[-- Attachment #2: alpha-tdep.c.diff --]
[-- Type: text/plain, Size: 2795 bytes --]
Index: alpha-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
retrieving revision 1.148
diff -u -p -r1.148 alpha-tdep.c
--- alpha-tdep.c 17 Feb 2005 13:49:48 -0000 1.148
+++ alpha-tdep.c 20 May 2005 01:14:42 -0000
@@ -1335,6 +1335,30 @@ alpha_fill_fp_regs (int regno, void *f0_
}
\f
+
+/* Return nonzero if the G_floating register value in REG is equal to
+ zero for FP control instructions. */
+
+static int
+fp_register_zero_p (LONGEST reg)
+{
+ /* Check that all bits except the sign bit are zero. */
+ const LONGEST zero_mask = ((LONGEST) 1 << 63) ^ -1;
+
+ return ((reg & zero_mask) == 0);
+}
+
+/* Return the value of the sign bit for the G_floating register
+ value held in REG. */
+
+static int
+fp_register_sign_bit (LONGEST reg)
+{
+ const LONGEST sign_mask = (LONGEST) 1 << 63;
+
+ return ((reg & sign_mask) != 0);
+}
+
/* alpha_software_single_step() is called just before we want to resume
the inferior, if we want to single-step it but there is no hardware
or kernel single-step support (NetBSD on Alpha, for example). We find
@@ -1350,6 +1374,7 @@ alpha_next_pc (CORE_ADDR pc)
unsigned int op;
int offset;
LONGEST rav;
+ char reg[8];
insn = alpha_read_insn (pc);
@@ -1379,7 +1404,9 @@ alpha_next_pc (CORE_ADDR pc)
}
/* Need to determine if branch is taken; read RA. */
- rav = (LONGEST) read_register ((insn >> 21) & 0x1f);
+ regcache_cooked_read (current_regcache, (insn >> 21) & 0x1f, reg);
+ rav = extract_signed_integer (reg, 8);
+
switch (op)
{
case 0x38: /* BLBC */
@@ -1415,7 +1442,32 @@ alpha_next_pc (CORE_ADDR pc)
goto branch_taken;
break;
- /* ??? Missing floating-point branches. */
+ /* Floating point branches. */
+
+ case 0x31: /* FBEQ */
+ if (fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
+ case 0x36: /* FBGE */
+ if (fp_register_sign_bit (rav) == 0 || fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
+ case 0x37: /* FBGT */
+ if (fp_register_sign_bit (rav) == 0 && ! fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
+ case 0x33: /* FBLE */
+ if (fp_register_sign_bit (rav) == 1 || fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
+ case 0x32: /* FBLT */
+ if (fp_register_sign_bit (rav) == 1 && ! fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
+ case 0x35: /* FBNE */
+ if (! fp_register_zero_p (rav))
+ goto branch_taken;
+ break;
}
}
next reply other threads:[~2005-05-20 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 2:34 Joel Brobecker [this message]
2005-05-20 3:35 ` Richard Henderson
2005-05-20 6:18 ` Daniel Jacobowitz
2005-05-20 12: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=20050520012055.GY1462@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