Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pierre.muller@ics-cnrs.unistra.fr, mark.kettenis@xs4all.nl,
	 	gdb-patches@sourceware.org
Subject: Re: PATCH: Support i386 without SSE
Date: Fri, 09 Apr 2010 13:16:00 -0000	[thread overview]
Message-ID: <o2t6dc9ffc81004090615x13222685rc1bf6cd446d7728d@mail.gmail.com> (raw)
In-Reply-To: <834ojl13ci.fsf@gnu.org>

On Fri, Apr 9, 2010 at 12:39 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 8 Apr 2010 15:28:56 -0700
>> From: "H.J. Lu" <hjl.tools@gmail.com>
>> Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>, mark.kettenis@xs4all.nl,
>>       gdb-patches@sourceware.org
>>
>> >> > Eli, Pierre, can you test wether this fixes the issues on Go32?
>> >>
>> >>  I tested the patch and it does
>> >> indeed fix the two problems that I
>> >> reported.
>> >
>> > Thanks for testing.
>>
>> I will check in my patch.
>
> Thanks.
>
>> >>   Nevertheless, there are still strange things:
>> >>   if you use 'maint print register-groups'
>> >> you will find out that
>> >> the SSE xmmX registers are still present as registers 32 to 40
>> >> and the ymmX as 41 to 48, but with empty names and a strange int0_t type.
>>
>> I think those are expected as they are reserved internally
>> and not visible to user.
>
> If this is a general feature, it's fine with me, but perhaps we should
> add a note about that to where 'maint print register-groups' is
> described in the manual, saying that it could also show registers
> which are not really supported by the target.  Just so that it doesn't
> cause confusion.
>
> Thanks.
>

How about this patch?


-- 
H.J.
--
2010-04-09  H.J. Lu  <hongjiu.lu@intel.com>

        * gdb.texinfo (maint print registers): Mention unavailable and
        invisible registers.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index bd2b441..6629526 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -29082,8 +29082,9 @@ Print @value{GDBN}'s internal register data structures.

 The command @code{maint print raw-registers} includes the contents of
 the raw register cache; the command @code{maint print cooked-registers}
-includes the (cooked) value of all registers; and the command
-@code{maint print register-groups} includes the groups that each
+includes the (cooked) value of all registers, including registers which
+aren't available on the target nor visible to user; and the
+command @code{maint print register-groups} includes the groups that each
 register is a member of.  @xref{Registers,, Registers, gdbint,
 @value{GDBN} Internals}.


  reply	other threads:[~2010-04-09 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 20:05 H.J. Lu
2010-04-07 20:12 ` H.J. Lu
2010-04-07 20:31   ` Eli Zaretskii
2010-04-08 19:08 ` Mark Kettenis
2010-04-08 20:33   ` Pierre Muller
     [not found]   ` <000c01cad75a$b751a490$25f4edb0$%muller@ics-cnrs.unistra.fr>
2010-04-08 21:37     ` Eli Zaretskii
2010-04-08 22:29       ` H.J. Lu
2010-04-09  7:41         ` Eli Zaretskii
2010-04-09 13:16           ` H.J. Lu [this message]
2010-04-09 15:08             ` Eli Zaretskii

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=o2t6dc9ffc81004090615x13222685rc1bf6cd446d7728d@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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