Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: jimb@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] i386 SSE registers
Date: Sun, 14 Dec 2003 15:34:00 -0000	[thread overview]
Message-ID: <200312141534.hBEFYXZQ008843@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <vt24qw4o8rz.fsf@zenia.home> (message from Jim Blandy on 13 Dec 2003 13:46:40 -0500)

   From: Jim Blandy <jimb@redhat.com>
   Date: 13 Dec 2003 13:46:40 -0500

   I'm not sure I understand how the various options you list would
   appear to the user.  It sounds like, in any proposal, the SSE
   registers would just have bogus values when they're not available.

Yup.  It's either

1a. All zeroes.

1b. All zeroes, but preserving any explicit (but otherwise pointless)
    changes made by the user.

2. Some faked values (presumably corresponding to a freshly
   initialized CPU).

   Is there some way that the SSE regs could instead cease to exist
   (i.e. "print $xmm0" would give you a void value, 'info regi sse'
   would give you an error message)?  Or is there some other
   non-invasive behavior which would make it clearer to the user what
   was going on?

You can't solve this via the architecture vector I think.  It's
possible to use the same GDB and use it to debug a program on a
machine without SSE and then later on a machine with SSE.

What we could do is add a per-register flag to the register cache that
says whether a register is actually present or not.  But that's quite
a bit of work I guess.  Don't think we should think about doing
something like that before the legacy stuff has been eradicated.

Mark


      reply	other threads:[~2003-12-14 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 17:06 Mark Kettenis
2003-12-13 18:49 ` Jim Blandy
2003-12-14 15:34   ` Mark Kettenis [this message]

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=200312141534.hBEFYXZQ008843@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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