From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ronald Hecht <ronald.hecht@uni-rostock.de>
Cc: cgen@sourceware.org
Subject: Re: Simulator and 24 Bit instructions
Date: Mon, 31 Jul 2006 15:27:00 -0000 [thread overview]
Message-ID: <20060731152727.GA10189@redhat.com> (raw)
In-Reply-To: <44CDC354.9010502@uni-rostock.de>
Hi -
> I'm having now problems with 24 Bit instructions in the simulator.
> [...]
> So 24 Bit instructions are a problem. I hacked
> case 24 : insn_value = (T2H_4 (insn_buf.words[0]) / 256) &
> 0x00ffffff; break;
It would be more transparent to explicitly fetch three bytes. But why
is base_length 24 rather than 8? It seems that you have come some way
since the posting of your .cpu file last week. It may help to post
your current version.
- FChE
next prev parent reply other threads:[~2006-07-31 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 8:44 Ronald Hecht
2006-07-31 15:27 ` Frank Ch. Eigler [this message]
2006-07-31 16:00 ` Ronald Hecht
2006-08-03 20:07 ` 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=20060731152727.GA10189@redhat.com \
--to=fche@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).