From: Christian Groessler <chris@groessler.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [patch/rfc] Delete sim/z8k/list.c
Date: Wed, 05 Jun 2002 14:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0206052302020.10179-100000@ds9.reckziegel.com> (raw)
In-Reply-To: <3CFA565A.2050609@cygnus.com>
On Sun, 2 Jun 2002, Andrew Cagney wrote:
> Following up the change:
>
> > 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".
>
> The attached patch deletes sim/z8k/list.c instead [re]generating its
> contents each time writecode is run. While it might make building the
> z8k simulator slower, I think it makes its maintenance much easier - one
> less generated file to contend with.
I agree.
> If no one sees problems, I'll commit it in a few days. The files
> generated by writecode appear to be identical with/without the change
> (but only if the before case has a freshly re-generated list.c, er, hmm
> .... :-).
What do you mean by that? The old list.c was definately wrong (since
z8k-opc.h was changed).
I tried your patch, and it works for me. Please commit.
regards,
chris
next prev parent reply other threads:[~2002-06-05 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 10:30 Andrew Cagney
2002-06-05 14:05 ` Christian Groessler [this message]
2002-06-05 14:52 ` Andrew Cagney
2002-06-06 8:53 ` Andrew Cagney
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=Pine.LNX.4.30.0206052302020.10179-100000@ds9.reckziegel.com \
--to=chris@groessler.org \
--cc=ac131313@cygnus.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