Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: klee@apple.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Print vector registers in natural format, not hex
Date: Sat, 12 Oct 2002 02:01:00 -0000	[thread overview]
Message-ID: <1438-Sat12Oct2002105650+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <22199F8A-DD36-11D6-B6D6-00039396EEB8@apple.com> (message from Klee Dienes on Fri, 11 Oct 2002 12:26:02 -0400)

> Date: Fri, 11 Oct 2002 12:26:02 -0400
> From: Klee Dienes <klee@apple.com>
> 
> Maybe something along the lines of:
> 
> @value{GDBN} always considers the contents of an ordinary register as an
> integer when the register is examined in this way.  Some machines have
> special registers that are predefined to have specific types (typically 
> floating
> point or vector registers); these registers are printed according to 
> their
> system-defined type.  There is no way to refer to the contents of an 
> ordinary
> register as a floating point value or vector type (although you can 
> @emph{print}
> it as a floating point value with @samp{print/f $@var{regname}}).

That's good, but perhaps an explicit reference to "info vector" and
"info float" would be useful.


  reply	other threads:[~2002-10-12  9:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 13:41 Klee Dienes
2002-10-04 13:52 ` Daniel Jacobowitz
2002-10-04 14:11   ` Klee Dienes
2002-10-04 14:36     ` Daniel Jacobowitz
2002-10-18 16:23       ` Elena Zannoni
2002-11-04 20:02         ` Klee Dienes
2002-11-04 20:34           ` Daniel Jacobowitz
2002-10-05 10:29 ` Eli Zaretskii
2002-10-05 13:03   ` Klee Dienes
2002-10-06 11:31     ` Eli Zaretskii
2002-10-11  9:26       ` Klee Dienes
2002-10-12  2:01         ` Eli Zaretskii [this message]
2002-10-21 17:23         ` Andrew Cagney
2002-10-18 16:37 ` Elena Zannoni
2002-11-05  0:48   ` Klee Dienes

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=1438-Sat12Oct2002105650+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@apple.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