From: Andrew Cagney <ac131313@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: gdb-patches@sources.redhat.com
Subject: z8k sim breakage
Date: Mon, 06 Jan 2003 22:28:00 -0000 [thread overview]
Message-ID: <3E1A02C6.2070607@redhat.com> (raw)
Alan,
I suspect the change:
2002-12-13 Alan Modra <amodra@bigpond.net.au>
* h8500-opc.h (h8500_table): Add missing initializers to quiet
warnings.
* pj-dis.c (print_insn_pj): Adjust for pj_opc_info_t change.
* pj-opc.c (pj_opc_info): Add braces around union initializer.
* z8kgen.c: Include "libiberty.h".
(opt, args, toks): Fix initializer warnings.
(chewname): Make "name" a char **. Return mnemonic trimmed of
operands.
(gas): Improve emitted "DO NOT EDIT" warning. Format emitted
opcode_entry_type, and make "nicename" and "name" const. Make
z8k_table const too. Formatting. Generate idx as gas needs it.
* z8k-opc.h: Regenerate.
broke the building of sim/z8k vis:
$ make
gcc -c -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1
-DDEFAULT_INLINE=0
-I/notnfs/cagney/GDB/src/sim/z8k/../../newlib/libc/sys/z8k -I.
-I/notnfs/cagney/GDB/src/sim/z8k -I../common
-I/notnfs/cagney/GDB/src/sim/z8k/../common -I../../include
-I/notnfs/cagney/GDB/src/sim/z8k/../../include -I../../bfd
-I/notnfs/cagney/GDB/src/sim/z8k/../../bfd -I../../opcodes
-I/notnfs/cagney/GDB/src/sim/z8k/../../opcodes -I../../intl
-I/notnfs/cagney/GDB/src/sim/z8k/../../intl -g -O2
/notnfs/cagney/GDB/src/sim/z8k/comped3.c
In file included from /notnfs/cagney/GDB/src/sim/z8k/comped3.c:26:
tc-gen3.h:68: redefinition of `sfop_2'
tc-gen3.h:46: `sfop_2' previously defined here
tc-gen3.h:91: redefinition of `sfop_2'
tc-gen3.h:68: `sfop_2' previously defined here
That sim's writecode program drags in the opcodes table and then uses it
to generate part of the simulator (hence my suspicion). I'm still
trying to figure out how that `wonderful' code works.
Anyway, off hand, what exactly did you change here? (perhaphs that will
explain what went wrong)
Also, was it because of a reported z8k bug or just a cleanup? (i'm also
looking for evidence of z8k life)
Andrew
next reply other threads:[~2003-01-06 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 22:28 Andrew Cagney [this message]
2003-01-06 23:03 ` Alan Modra
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=3E1A02C6.2070607@redhat.com \
--to=ac131313@redhat.com \
--cc=amodra@bigpond.net.au \
--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