From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: [PATCH] Re: [rfa/amd64] Zero fill 32-bit registers
Date: Sat, 28 Feb 2004 21:56:00 -0000 [thread overview]
Message-ID: <200402282155.i1SLtqGg006156@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <4040FC93.9000100@gnu.org> (message from Andrew Cagney on Sat, 28 Feb 2004 15:39:47 -0500)
Date: Sat, 28 Feb 2004 15:39:47 -0500
From: Andrew Cagney <cagney@gnu.org>
> Could you live with just zero-extending the 16 general-purpose
> registers and the instruction pointer? I'll implement it for you.
It is certainly an improvement! Can you test it?
I've tested the attached on SuSE 8.2, with -m32. No changes in the
testoutput for me, but the threaded stuff doesn't work very well on
the system (and probably no at all in on 32x64-bit). I committed it
anyway, since I can't imagine this making things worse for the
threaded stuff if it works for the non-threaded stuff. I'd appreciate
it if you could test whether this fixed the problems you were seeing.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* amd64-nat.c: Include "gdb_string.h".
(amd64_collect_native_gregset): Zero-extend the 32-bit
general-purpose registers and %eip.
Index: amd64-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-nat.c,v
retrieving revision 1.4
diff -u -p -r1.4 amd64-nat.c
--- amd64-nat.c 25 Feb 2004 20:59:12 -0000 1.4
+++ amd64-nat.c 28 Feb 2004 21:54:26 -0000
@@ -24,6 +24,7 @@
#include "regcache.h"
#include "gdb_assert.h"
+#include "gdb_string.h"
#include "i386-tdep.h"
#include "amd64-tdep.h"
@@ -128,7 +129,17 @@ amd64_collect_native_gregset (const stru
int i;
if (gdbarch_ptr_bit (gdbarch) == 32)
- num_regs = amd64_native_gregset32_num_regs;
+ {
+ num_regs = amd64_native_gregset32_num_regs;
+
+ /* Make sure %eax, %ebx, %ecx, %edx, %esi, %edi, %ebp, %esp and
+ %eip get zero-extended to 64 bits. */
+ for (i = 0; i <= I386_EIP_REGNUM; i++)
+ {
+ if (regnum == -1 || regnum == i)
+ memset (regs + amd64_native_gregset_reg_offset (i), 0, 8);
+ }
+ }
if (num_regs > NUM_REGS)
num_regs = NUM_REGS;
next prev parent reply other threads:[~2004-02-28 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 1:22 Andrew Cagney
2004-02-28 10:46 ` Mark Kettenis
2004-02-28 15:17 ` Andrew Cagney
2004-02-28 17:35 ` Mark Kettenis
2004-02-28 19:18 ` Andrew Cagney
2004-02-28 20:26 ` Mark Kettenis
2004-02-28 20:40 ` Andrew Cagney
2004-02-28 21:56 ` Mark Kettenis [this message]
2004-02-29 23:11 ` [PATCH] " Andrew Cagney
2004-02-29 23:45 ` Mark Kettenis
2004-03-02 16:10 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
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=200402282155.i1SLtqGg006156@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=cagney@gnu.org \
--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