From: Doug Evans <dje@sebabeach.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: cgen@sourceware.org
Subject: Re: cgen -> opcodes problem
Date: Mon, 28 Dec 2009 19:04:00 -0000 [thread overview]
Message-ID: <4B39014D.4000203@sebabeach.org> (raw)
In-Reply-To: <20091227081006.GA23270@doriath.ww600.siemens.net>
Dmitry Eremin-Solenikov wrote:
> Hello all,
>
> I'm back to my m68hc08 binutils port done via cgen.
> Recently I've again stumbled upon a problem with instructions,
> whose base? length != ISA base length.
>
> E.g. in the attached stripped test case, the 'ttt' instruction either
> (should be assembled as 0x9E 0xF1) is misencoded as 0xsmth 0x00.
> Is this my fault? Or is this the expected behaviour and I should define
> f-seccode in some other way?
>
> Could you please help me?
>
>
Hi. cgen currently doesn't handle instructions with opcode bits beyond
the base insn size very well. I have a sandbox with this fixed, but
it'll be awhile (month or more?) before it all gets checked in.
In the meantime, setting base-insn-bitsize to 16 may work. [It *should*
work, but there may be attributes of your port I haven't taken into
account.]
next prev parent reply other threads:[~2009-12-28 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 8:10 Dmitry Eremin-Solenikov
2009-12-28 19:04 ` Doug Evans [this message]
2009-12-28 21:30 ` Dmitry Eremin-Solenikov
2009-12-28 21:57 ` Doug Evans
2009-12-28 22:59 ` Dmitry Eremin-Solenikov
2010-02-24 14:55 ` Dmitry Eremin-Solenikov
2010-02-24 16:49 ` Doug Evans
2010-02-26 11:39 ` Dmitry Eremin-Solenikov
2010-03-05 22:15 ` Doug Evans
2010-03-05 22:48 ` Dmitry Eremin-Solenikov
2010-03-05 22:51 ` 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=4B39014D.4000203@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.org \
--cc=dbaryshkov@gmail.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).