From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: Doug Evans <dje@transmeta.com>, <gdb-patches@sources.redhat.com>,
<cgen@sources.redhat.com>
Subject: Re: [Sim] New sim/common/cgen.sh
Date: Mon, 04 Dec 2000 10:55:00 -0000 [thread overview]
Message-ID: <14891.59510.53616.923378@casey.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012042057050.4684-100000@moshpit.cygnus.com>
Ben Elliston writes:
> Also, while the existing script has problems with parallel makes, your
> version has even worse problems. You might want to fix that.
>
> I have also just fixed genmloop.sh so that it has an -outfile-suffix option.
> This allows the generated files to form unique filenames -- so it, too, can
> be run by a parallel make.
Can't this problem be solved without adding an option?
next prev parent reply other threads:[~2000-12-04 10:55 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 [this message]
2000-12-04 13:11 ` Ben Elliston
2000-12-04 18:40 ` Doug Evans
2000-12-04 19:29 ` Ben Elliston
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=14891.59510.53616.923378@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bje@redhat.com \
--cc=cgen@sources.redhat.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).