From: Nathan Froyd <froydnj@codesourcery.com>
To: cgen@sourceware.org
Subject: insn semantics required?
Date: Mon, 24 Jan 2011 14:24:00 -0000 [thread overview]
Message-ID: <20110124142354.GE6247@codesourcery.com> (raw)
I've been looking through the documentation and couldn't determine
conclusively whether defining the semantics of an insn is required. Is
it? Auto-magically defining a simulator seems less useful in this day
and age, but an auto-generated assembler and disassembler seems quite
useful.
I suppose as a stopgap one could simply provide an uninteresting
semantics for each insn.
-Nathan
next reply other threads:[~2011-01-24 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 14:24 Nathan Froyd [this message]
2011-01-24 14:53 ` Frank Ch. Eigler
2011-01-24 14:59 ` Jean-Marc Saffroy
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=20110124142354.GE6247@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=cgen@sourceware.org \
/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).