From: Jim Blandy <jimb@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] i386 SSE registers
Date: Sat, 13 Dec 2003 18:49:00 -0000 [thread overview]
Message-ID: <vt24qw4o8rz.fsf@zenia.home> (raw)
In-Reply-To: <200312121706.hBCH6mIh011419@elgar.kettenis.dyndns.org>
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. 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?
next prev parent reply other threads:[~2003-12-13 18:49 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 [this message]
2003-12-14 15:34 ` Mark Kettenis
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=vt24qw4o8rz.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@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