public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: <gdb-patches@sources.redhat.com>, <cgen@sources.redhat.com>
Subject: Re: [Sim] New sim/common/cgen.sh
Date: Mon, 04 Dec 2000 19:29:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0012051428270.7250-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <14892.21907.916077.737133@casey.transmeta.com>

   The theory is that the script is already being passed something it can
   use.

The same could be said for determining the input filename (ie. mloop.in),
but we provide the flexibility to specify *that*.  There is even a comment
in genmloop.sh that says that it would be useful to provide options to
specify the output filenames (both of them) in the future.

Ben

      reply	other threads:[~2000-12-04 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-03 19:24 Ben Elliston
2000-12-03 21:28 ` Doug Evans
2000-12-03 23:49   ` Ben Elliston
2000-12-04  1:47   ` Ben Elliston
2000-12-04  1:57     ` Ben Elliston
2000-12-04 10:55       ` Doug Evans
2000-12-04 13:11         ` Ben Elliston
2000-12-04 18:40           ` Doug Evans
2000-12-04 19:29             ` Ben Elliston [this message]

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.0012051428270.7250-100000@moshpit.cygnus.com \
    --to=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).