public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: some opcode files could be regenerated (e.g. <cpu>-desc.c)
Date: Mon, 21 Apr 2003 09:13:00 -0000	[thread overview]
Message-ID: <m365p8gqof.fsf@localhost.localdomain> (raw)
In-Reply-To: <16034.49691.964419.224679@casey.transmeta.com>

Hi Doug,

>  > Are you asking if anyone minds you regenerating the files, or would
>  > you like me to regenerate them for you ?  I'm happy either way.
> 
> WELL ....  if you're offering ... :-)
> 
> But no I was going to (and will do it).

Well, I would prefer it if you did it, because I think that there are
some problems with the cgen/cpu/iq2000.cpu file, (the generated files
do not compile), and I think that you would be more able than I to
sort out the problem.

Cheers
        Nick

  reply	other threads:[~2003-04-21  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 18:27 Doug Evans
2003-04-20  8:52 ` Nick Clifton
2003-04-20 15:52   ` Doug Evans
2003-04-21  9:13     ` Nick Clifton [this message]
2003-04-22 18:53       ` Doug Evans
2003-04-23  8:15         ` Nick Clifton

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=m365p8gqof.fsf@localhost.localdomain \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).