From: Eli Zaretskii <eliz@is.elta.co.il>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips: Fix "info registers" output
Date: Thu, 21 Jun 2001 09:29:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010621192927.12321A-100000@is> (raw)
In-Reply-To: <20010621083624.A9719@nevyn.them.org>
On Thu, 21 Jun 2001, Daniel Jacobowitz wrote:
> - the decoding of double-precision arguments was completely broken.
> In addition to copying unallocated memory, and getting the byte order
> wrong, we tried to decode two four-byte pointers to data instead of the
> data itself. Thus the doubles were generally 'nan'.
>
> - If the number of GPRs fit precisely on an integer number of rows,
> blank space would be printed without even a trailing newline, and the
> prompt would be mysteriously indented.
I cannot reproduce this on SGI Irix 6.5, which also uses mips-tdeps.c. I
used a small throw-away FP program and all the FP registers printed
perfectly okay. No NaNs at all. info registers seems also okay.
Perhaps I didn't try exactly what you did. Any further hints?
next prev parent reply other threads:[~2001-06-21 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010619225007.A10141@nevyn.them.org>
2001-06-20 7:19 ` Andrew Cagney
2001-06-21 0:45 ` Eli Zaretskii
2001-06-21 8:37 ` Daniel Jacobowitz
2001-06-21 9:29 ` Eli Zaretskii [this message]
2001-06-21 9:44 ` Daniel Jacobowitz
2001-06-21 12:00 ` Eli Zaretskii
2001-06-21 13:12 ` Daniel Jacobowitz
2001-06-21 14:22 ` Don Howard
2002-03-07 13:59 ` Daniel Jacobowitz
2002-03-09 18:05 ` Andrew Cagney
2002-03-09 22:58 ` Daniel Jacobowitz
2002-03-10 8:30 ` Andrew Cagney
2002-03-10 9:00 ` Daniel Jacobowitz
2002-03-10 9:46 ` Andrew Cagney
2002-03-10 11:30 ` Daniel Jacobowitz
2002-03-10 12:45 ` Andrew Cagney
2002-03-10 14:26 ` Daniel Jacobowitz
2002-03-10 15:18 ` Andrew Cagney
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=Pine.SUN.3.91.1010621192927.12321A-100000@is \
--to=eliz@is.elta.co.il \
--cc=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.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