Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Re: [rfa/amd64] Zero fill 32-bit registers
Date: Sun, 29 Feb 2004 23:11:00 -0000	[thread overview]
Message-ID: <404271AE.5000102@gnu.org> (raw)
In-Reply-To: <200402282155.i1SLtqGg006156@elgar.kettenis.dyndns.org>

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

>    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.

The segment registers have the same problem, is the attached ok? 6.1? 
With it applied I get test results that approach i386.

Andrew


[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 797 bytes --]

2004-02-29  Andrew Cagney  <cagney@redhat.com>

	* amd64-nat.c (amd64_collect_native_gregset): Zero-extend the
	32-bit segment registers.

Index: amd64-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-nat.c,v
retrieving revision 1.5
diff -u -r1.5 amd64-nat.c
--- amd64-nat.c	28 Feb 2004 21:55:48 -0000	1.5
+++ amd64-nat.c	29 Feb 2004 23:08:08 -0000
@@ -139,6 +139,12 @@
 	  if (regnum == -1 || regnum == i)
 	    memset (regs + amd64_native_gregset_reg_offset (i), 0, 8);
 	}
+      /* Ditto for %cs, %ss, %ds, %es, %fs, and %gs.  */
+      for (i = I386_CS_REGNUM; i < I386_ST0_REGNUM; i++)
+	{
+	  if (regnum == -1 || regnum == i)
+	    memset (regs + amd64_native_gregset_reg_offset (i), 0, 8);
+	}
     }
 
   if (num_regs > NUM_REGS)

  reply	other threads:[~2004-02-29 23:11 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             ` [PATCH] " Mark Kettenis
2004-02-29 23:11               ` Andrew Cagney [this message]
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=404271AE.5000102@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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