From: Dave Brolley <brolley@redhat.com>
To: Ronald Hecht <ronald.hecht@uni-rostock.de>
Cc: cgen@sourceware.org
Subject: Re: Simulator: base_insn and insn in decode.c
Date: Thu, 03 Aug 2006 22:08:00 -0000 [thread overview]
Message-ID: <44D273E8.4040006@redhat.com> (raw)
In-Reply-To: <44D270CF.30506@redhat.com>
I forgot to address your other question which was about the difficulty
of setting entire_insn before decoding. It's a bit of a chicken and egg
situation isnt'y it? You can't set entire insn properly until you know
something about the insn, but you can't call decode without setting
entire_insn properly.
Your method of calling decode twice won't work because of this.
Most existing ports determine the insn length by looking at a few bits
in base_insn and use this information to fill entire_insn.
I'm wondering if the decoder shouldn't be redesigned so that all it
takes is base_insn, which should be all that is necessary to identify
the insn. The extractors for each format would then read any additional
bytes as needed. There is already support for this for ISAs with insns
which are longer than an insn word.
Dave
next prev parent reply other threads:[~2006-08-03 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 11:58 Ronald Hecht
2006-08-03 21:55 ` Dave Brolley
2006-08-03 22:08 ` Dave Brolley [this message]
2006-08-07 14:39 ` Ronald Hecht
2006-08-07 14:53 ` Ronald Hecht
2006-08-14 21:19 ` Dave Brolley
2006-08-15 8:39 ` Ronald Hecht
2006-08-04 8:51 ` Ronald Hecht
2006-08-14 20:34 ` Dave Brolley
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=44D273E8.4040006@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=ronald.hecht@uni-rostock.de \
/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).