Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: klee@mit.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Print vector registers in natural format, not hex
Date: Sat, 05 Oct 2002 10:29:00 -0000	[thread overview]
Message-ID: <9003-Sat05Oct2002202855+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <B4580F12-D7D9-11D6-866A-00039396EEB8@mit.edu> (message from Klee Dienes on Fri, 4 Oct 2002 16:41:48 -0400)

> Date: Fri, 4 Oct 2002 16:41:48 -0400
> From: Klee Dienes <klee@mit.edu>
> 
> The attached patch changes the algorithm so that all vector and float
> registers are printed in natural format, followed by "(raw
> 0xffffffff)".  I've attached samples of the output before and after the
> patch; the behavior of GDB should be unchanged except for vector
> variables.  There's no effect on the results from running the testsuite
> on powerpc-apple-darwin or i386-unknown-gnu-linux; it does require a
> testsuite change to altivec-regs.exp on powerpc-unknown-gnu-linux.

Thanks for this contribution.  If it is approved, please also change
the relevant parts of the user manual to reflect this change.


  parent reply	other threads:[~2002-10-05 17:29 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 [this message]
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
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=9003-Sat05Oct2002202855+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@mit.edu \
    /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