From: Christian Groessler <chris@groessler.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] z8k fixes
Date: Tue, 21 May 2002 07:35:00 -0000 [thread overview]
Message-ID: <87znytzs4x.fsf@panther.aladdin.de> (raw)
On Mon, 20 May 2002, Andrew Cagney wrote:
> > this patch fixes some small problems with the z8k simulator. I don't
> > have copyright assignments for gdb, but I hope the patch is small
> > enough to get integrated without.
> >
>
> > sim/z8k/ChangeLog:
> >
> > 2002-05-07 Christian Groessler <chris@groessler.org>
> >
> > * list.c: Regenerated with current opcodes/z8k-opc.h.
>
> How do I do this? I was thinking that the patch was too big but, if the
> bulk is generated then yes, it is ok.
It is generated. Edit sim/z8k/writecode.c and set the DIRTY_HACK
define to 1. I think it's not really needed anymore, but the old
list.c was generated with the same define.
Then compile writecode.c (it will also be compiled if you build gdb
for z8k-coff) and do a "./writecode -m > list.c".
> Would it be possible for you to get an assignment? (if there is a
> possability then contact jimb (CC'd).
Depending on the gdb changes needed (see below), I'll do.
> The z8k is due for an overaul (or it may be deleted).
What should be changed/fixed there?
regards,
chris
next reply other threads:[~2002-05-21 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 7:35 Christian Groessler [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 9:09 Christian Groessler
2002-05-19 21:42 ` Andrew Cagney
2002-06-02 7:58 ` Andrew Cagney
2002-06-05 14:09 ` Christian Groessler
2002-06-05 14:59 ` Andrew Cagney
2002-06-05 16:29 ` Christian Groessler
2002-06-06 8:56 ` Andrew Cagney
2002-06-06 14:08 ` Christian Groessler
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=87znytzs4x.fsf@panther.aladdin.de \
--to=chris@groessler.org \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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