From: DJ Delorie <dj@redhat.com>
To: dje@sebabeach.org
Cc: geoffk@geoffk.com, cgen@sources.redhat.com
Subject: Re: opcode bits beyond base-insn-bitsize
Date: Tue, 24 Dec 2002 09:53:00 -0000 [thread overview]
Message-ID: <200212241752.gBOHqxJ28997@greed.delorie.com> (raw)
In-Reply-To: <20021224055735.2F216B539@seba.sebabeach.org> (message from Doug Evans on Mon, 23 Dec 2002 21:57:35 -0800 (PST))
> Can anyone remember what the details are?
> i.e. what didn't work? assembler? disassembler? simulator?
xstormy16 has both 16bit and 32bit opcodes, and some of the 32bit
opcodes have decodable bits in the second half. The base-insn-bitsize
is used to set up the masks and such, so it needs to be at least as
big as the largest decodable bits.
The tricky bit is when the 32-bit opcodes are mixed endian (i.e. the
first 16 bits are swapped independently of the second 16 bits,
resulting in ABCD or BADC endian, but not DCBA).
next prev parent reply other threads:[~2002-12-24 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 21:51 Doug Evans
2002-12-24 9:53 ` DJ Delorie [this message]
2002-12-24 10:08 ` Doug Evans
2002-12-24 10:11 ` DJ Delorie
2002-12-24 10:27 ` 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=200212241752.gBOHqxJ28997@greed.delorie.com \
--to=dj@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@sebabeach.org \
--cc=geoffk@geoffk.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).