From: Fred Fish <fnf@fishpond.ninemoons.com>
To: gdb-patches@sources.redhat.com
Cc: fnf@ninemoons.com
Subject: [RFA] patch for mips gdb build failure with latest gcc
Date: Wed, 07 Nov 2001 10:37:00 -0000 [thread overview]
Message-ID: <200111180417.fAI4HtH30179@fishpond.ninemoons.com> (raw)
Gdb for mips does not currently build with the latest gcc. The error
message is:
In file included from support.c:26:
sim-main.h:370: unnamed fields of type other than struct or union are not allowed
The problem is an enum declaration inside a struct declaration, which
is apparently now illegal. This patch fixes it.
2001-11-17 Fred Fish <fnf@redhat.com>
* sim-main.h (float_operation): Move enum declaration outside
of _sim_cpu struct declaration.
Index: sim-main.h
===================================================================
RCS file: /cvs/src/src/sim/mips/sim-main.h,v
retrieving revision 1.6
diff -u -p -r1.6 sim-main.h
--- sim-main.h 2001/04/12 14:53:20 1.6
+++ sim-main.h 2001/11/18 04:16:54
@@ -297,6 +297,13 @@ do { \
} while (0)
+enum float_operation
+ {
+ FLOP_ADD, FLOP_SUB, FLOP_MUL, FLOP_MADD,
+ FLOP_MSUB, FLOP_MAX=10, FLOP_MIN, FLOP_ABS,
+ FLOP_ITOF0=14, FLOP_FTOI0=18, FLOP_NEG=23
+ };
+
struct _sim_cpu {
@@ -361,13 +368,6 @@ struct _sim_cpu {
#endif
-
-enum float_operation
- {
- FLOP_ADD, FLOP_SUB, FLOP_MUL, FLOP_MADD,
- FLOP_MSUB, FLOP_MAX=10, FLOP_MIN, FLOP_ABS,
- FLOP_ITOF0=14, FLOP_FTOI0=18, FLOP_NEG=23
- };
/* To keep this default simulator simple, and fast, we use a direct
vector of registers. The internal simulator engine then uses
next reply other threads:[~2001-11-18 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 10:37 Fred Fish [this message]
2001-11-07 10:43 ` Andrew Cagney
2001-11-07 11:31 ` Daniel Jacobowitz
2001-11-07 12:42 ` Fred Fish
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=200111180417.fAI4HtH30179@fishpond.ninemoons.com \
--to=fnf@fishpond.ninemoons.com \
--cc=fnf@ninemoons.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