From: Johan Rydberg <jrydberg@night.trouble.net>
To: <cgen@sources.redhat.com>
Cc: <jrydberg@night.trouble.net>
Subject: make CGEN a less moving target?
Date: Tue, 10 Dec 2002 08:48:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0212101742570.1967-100000@night> (raw)
Hi fellow CGEN-hackers.
From what I've seen it seems that CGEN have matured to the point
where it maybe is time to write a list of what should be included
in a CPU description, and where. Maybe list all keywords and such.
The reason for this is that maybe someone would like to write a parser
for .cpu-files, and not use the Scheme-sources provided by Red Hat, Inc.
(define-insn ...) and similar seems pretty "stable", but there seem
to be a lot of confusion regarding the (define-isa ...) fields.
brgds,
johan
next reply other threads:[~2002-12-10 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 8:48 Johan Rydberg [this message]
2002-12-10 9:33 ` Doug Evans
2002-12-10 17:06 ` Johan Rydberg
2002-12-11 2:39 ` Manuel Kessler
2002-12-11 4:18 ` Frank Ch. Eigler
2002-12-11 13:36 ` Doug Evans
2002-12-11 13:42 ` Frank Ch. Eigler
2002-12-11 13:50 ` Doug Evans
2002-12-11 13:57 ` Frank Ch. Eigler
2002-12-11 14:25 ` Doug Evans
2002-12-11 10:08 ` 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=Pine.GSO.4.33.0212101742570.1967-100000@night \
--to=jrydberg@night.trouble.net \
--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).