From: Jean-Marc Saffroy <jean-marc.saffroy@joguin.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: cgen@sourceware.org
Subject: Re: insn semantics required?
Date: Mon, 24 Jan 2011 14:59:00 -0000 [thread overview]
Message-ID: <4D3D93C9.9010605@joguin.com> (raw)
In-Reply-To: <20110124142354.GE6247@codesourcery.com>
Hi Nathan,
On 01/24/2011 03:23 PM, Nathan Froyd wrote:
> I've been looking through the documentation and couldn't determine
> conclusively whether defining the semantics of an insn is required. Is
> it?
The syntax requires that you define something, although I think "()"
will do if you don't built a simulator. Otherwise, as you noted, a
simple "(nop)" will definitely be sufficient.
> Auto-magically defining a simulator seems less useful in this day
> and age, but an auto-generated assembler and disassembler seems quite
> useful.
It really depends if you have a platform available for testing. A
simulator (auto-generated or not) is very convenient to run the gcc test
suite for regression testing.
Cheers,
JM
prev parent reply other threads:[~2011-01-24 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 14:24 Nathan Froyd
2011-01-24 14:53 ` Frank Ch. Eigler
2011-01-24 14:59 ` Jean-Marc Saffroy [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=4D3D93C9.9010605@joguin.com \
--to=jean-marc.saffroy@joguin.com \
--cc=cgen@sourceware.org \
--cc=froydnj@codesourcery.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).