From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Don Howard <dhoward@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips: Fix "info registers" output
Date: Sun, 10 Mar 2002 15:18:00 -0000 [thread overview]
Message-ID: <3C8BE9AD.5060300@cygnus.com> (raw)
In-Reply-To: <20020310172609.B9299@nevyn.them.org>
> Right now, for MIPS, builtin_type_double always means "whichever of
> builtin_type_ieee_double_{big,little} is appropriate" and likewise
> for builtin_type_float. (I note in passing that the type_ieee
> variables are not referenced. Anywhere. Only the floatformats are.)
Yes, it is a bug. MIPS integer registers have been (mostly?) changed to
the correct uint32 et.al. That fixed problems when debugging -mlong64
-mlong32 etc code.
> All I could see changed in mips-tdep.c would be to explicitly state
> that, and I don't really see the point, given the MIPS FP models we
> support. That's why I didn't see the need for the FIXME in question.
> Perhaps I'm not understanding you...?
It is one of those things where the ``right thing'' may not appear to
have an immediate return.
enjoy,
Andrew
prev parent reply other threads:[~2002-03-10 23:18 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
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 [this message]
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=3C8BE9AD.5060300@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dhoward@redhat.com \
--cc=drow@mvista.com \
--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