From: "Frank Ch. Eigler" <fche@redhat.com>
To: Michael Chapman <Michael.Chapman@synopsys.com>
Cc: cgen@sources.redhat.com
Subject: Re: Weirdness in disassembly
Date: Fri, 27 Sep 2002 08:41:00 -0000 [thread overview]
Message-ID: <20020927114148.D17426@redhat.com> (raw)
In-Reply-To: <NEBBIAJILEHBJOLKLAGOEEFOCIAA.michaelc@synopsys.com>; from Michael.Chapman@synopsys.com on Fri, Sep 27, 2002 at 05:19:33PM +0200
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Hi -
On Fri, Sep 27, 2002 at 05:19:33PM +0200, Michael Chapman wrote:
> [...]
> My mistake somewhere. Not sure when though. The opcode
> for the 32 bit instruction is the same as that for
> the 16 bit variant of it (well it was in how I had typed
> it)!
>
> Fixed that now. And I now get the correct disassembly.
Good stuff.
CGEN would benefit from improved detection of this sort of error.
If you were to generate a simulator kernel, you'd have been told of
the ambiguity.
> Now what values should I have for the instruction lengths?
> Obviously at least one of them has to be 16 bits for
> not skipping over to much when decoding junk.
Since a real program should not contain junk, a specific choice for
the other variables is not that important. Go with whatever
working numbers you prefer. The base-insn-size is the biggie.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next parent reply other threads:[~2002-09-27 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NEBBIAJILEHBJOLKLAGOOEFNCIAA.michaelc@synopsys.com>
[not found] ` <NEBBIAJILEHBJOLKLAGOEEFOCIAA.michaelc@synopsys.com>
2002-09-27 8:41 ` Frank Ch. Eigler [this message]
2002-09-27 7:46 Michael Chapman
2002-09-27 7:50 ` Frank Ch. Eigler
2002-09-27 8:02 ` Michael Chapman
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=20020927114148.D17426@redhat.com \
--to=fche@redhat.com \
--cc=Michael.Chapman@synopsys.com \
--cc=cgen@sources.redhat.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).