From: Eric Christopher <echristo@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix thinko in mips-tdep.c
Date: Fri, 10 May 2002 18:57:00 -0000 [thread overview]
Message-ID: <1021082112.6111.4.camel@ghostwheel.cygnus.com> (raw)
Daniel had a small thinko when writing the support for
mips_double(single)_register_type. This should fix it.
OK?
-eric
ps. I dont' think I have write after approval for gdb so someone should
check this in :)
--
I will not carve gods
2002-05-10 Eric Christopher <echristo@redhat.com>
* mips-tdep.c (mips_double_register_type): Fix thinko.
(mips_single_register_type): Ditto.
Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.72
diff -u -p -w -r1.72 mips-tdep.c
--- mips-tdep.c 9 May 2002 22:26:00 -0000 1.72
+++ mips-tdep.c 11 May 2002 01:52:28 -0000
@@ -2744,7 +2744,7 @@ mips_pop_frame (void)
static struct type *
mips_float_register_type (void)
{
- if (TARGET_BYTE_ORDER == BFD_BIG_ENDIAN)
+ if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
return builtin_type_ieee_single_big;
else
return builtin_type_ieee_single_little;
@@ -2753,7 +2753,7 @@ mips_float_register_type (void)
static struct type *
mips_double_register_type (void)
{
- if (TARGET_BYTE_ORDER == BFD_BIG_ENDIAN)
+ if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
return builtin_type_ieee_double_big;
else
return builtin_type_ieee_double_little;
@@ -4979,4 +4979,3 @@ that would transfer 32 bits for some reg
When non-zero, mips specific debugging is enabled.", &setdebuglist),
&showdebuglist);
}
-
next reply other threads:[~2002-05-11 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 18:57 Eric Christopher [this message]
2002-05-10 19:16 ` Andrew Cagney
2002-05-10 21:00 ` Daniel Jacobowitz
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=1021082112.6111.4.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.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