From: Doug Evans <dje@sebabeach.org>
To: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: machine generated documentation for cgen ports
Date: Wed, 11 Jun 2003 07:48:00 -0000 [thread overview]
Message-ID: <20030611075113.49D26B536@mail.sebabeach.org> (raw)
There's still a TON of work to be done before the documentation
is usable to more than just the maintainers of the port,
and what's there now may only be of MARGINAL use to port maintainers.
If one doesn't have access to a real reference manual and one wants to look
at the layout of a particular instruction, what's there now is potentially
useful. One obviously has to keep in mind that what's there isn't
authoritative.
Anyways I'm at a needed stopping point, so fyi ...
If you check the bottom of the cgen home page http://sources.redhat.com/cgen/
you'll see links to documentation generated from the cpu files.
Feedback is certainly welcome.
next reply other threads:[~2003-06-11 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 7:48 Doug Evans [this message]
2003-06-11 12:34 ` Ben Elliston
2003-06-11 15:50 ` Doug Evans
2003-06-11 20:53 ` Ben Elliston
2003-06-11 21:17 ` Doug Evans
2003-06-13 1:17 ` 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=20030611075113.49D26B536@mail.sebabeach.org \
--to=dje@sebabeach.org \
--cc=binutils@sources.redhat.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).