public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Carl Frankel <carl.frankel@ubicom.com>
Cc: "'cgen@sources.redhat.com'" <cgen@sources.redhat.com>
Subject: Re: CGEN output files
Date: Fri, 09 Mar 2001 19:03:00 -0000	[thread overview]
Message-ID: <20010309220315.A20081@redhat.com> (raw)
In-Reply-To: <470AE13EFEA7D31197C000508B139C67C7BF90@fenway.scenix.com>

Hi -

On Fri, Mar 09, 2001 at 04:16:14PM -0800, Carl Frankel wrote:
: Question:  Does CGEN produce .l/.y files for the assembler
:            as a part of its output?  [...]

Do you mean lex/yacc input files?  No.  CGEN-based assemblers
use a less formal run-time parser system built into the opcodes
library and to a lesser extent gas.


: I ask this as a cpu verifier.  I need to generate a 
: directed/random instruction sequence generator  [...]

You may find the existing assembler test case generator
of use.  See cgen's gas-test module and Makefile target.
It is fairly simpleminded (especially with regard to the
lack of diversity in the operand values), but with perhaps
not much Scheme code, it could be made to emit a stream of
randomized instructions.  


- FChE
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6qZlzVZbdDOm/ZT0RApS1AJ9JTC4AIhp5RIjl6BZwlsWAUyM+EQCfXAYQ
18oS5iFPbp/vHlvJ2COXUSo=
=n9IG
-----END PGP SIGNATURE-----

  reply	other threads:[~2001-03-09 19:03 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 [this message]
2001-03-12 20:22   ` Doug Evans
2001-03-12 20:25 ` Doug Evans

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=20010309220315.A20081@redhat.com \
    --to=fche@redhat.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).