From: Doug Evans <dje@transmeta.com>
To: Carl Frankel <carl.frankel@ubicom.com>
Cc: "'cgen@sources.redhat.com'" <cgen@sources.redhat.com>
Subject: CGEN output files
Date: Mon, 12 Mar 2001 20:25:00 -0000 [thread overview]
Message-ID: <15021.41236.113680.956874@casey.transmeta.com> (raw)
In-Reply-To: <470AE13EFEA7D31197C000508B139C67C7BF90@fenway.scenix.com>
Carl Frankel writes:
>
> Question: Does CGEN produce .l/.y files for the assembler
> as a part of its output? If not now, is this
> planned, and if so, in what time frame, more or
> less.
>
> I ask this as a cpu verifier. I need to generate a
> directed/random instruction sequence generator, and
> having .l/.y files to augment will be a tremendous
> time savings in creating the sequence generator.
It should be straightforward to take the existing testcase generator
and enhance it to suit such purposes.
[assuming you know Scheme, but it's a joy to program in anyway]
prev parent reply other threads:[~2001-03-12 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 16:19 Carl Frankel
2001-03-09 19:03 ` Frank Ch. Eigler
2001-03-12 20:22 ` Doug Evans
2001-03-12 20:25 ` Doug Evans [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=15021.41236.113680.956874@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=carl.frankel@ubicom.com \
--cc=cgen@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).