public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Doug Evans <dje@sebabeach.org>
Cc: cgen@sources.redhat.com
Subject: Re: Instruction w/ prefix
Date: Mon, 19 Oct 2009 13:29:00 -0000	[thread overview]
Message-ID: <4ADC6A35.4020709@gmail.com> (raw)
In-Reply-To: <4AD7ABC4.3080105@sebabeach.org>

Hello,

Doug Evans wrote:
> Dmitry Eremin-Solenikov wrote:
>> Hello,
>>
>> I'm using cgen to create binutils port for the CISC architecture
>> (M68HC(S)08 if somebody cares). I've stumbled upon one problem: the is
>> an instruction prefix which can change meaning
>> of the next instruction (basically it then uses SP register instead of 
>> IX one).
>>
>> What is the most clean way to do this w/ cgen? I can of course
>> duplicate instruction fields, counting another byte in the beginning,
>> instructions, etc.. This will permit me to catch illegal combinations.
>> OTOH it doesn' look like completely clean idea.
>>
>> What would you suggest?
>>
>>   
> 
> Hi.  Sorry for the slow reply.
> 
> I think the right solution (which I wouldn't wait for) is to extend cgen 
> to handle instruction prefixes.

Do you have any ideas how to implement (or at least design) this?

As for me, the prefix just changes the addressing (prefixed instruction
just uses SP as a base instead of IX register).

> In the meantime, I would treat the prefix as its own instruction.

Yep, I've tried this approach. However I've stumbled upon the fact that
cgen just sums all specified values, thus leading me into problems.

I'm currently looking into how to overcome this. Maybe you can suggest a 
  sample which I can look upon?

-- 
With best wishes
Dmitry

  reply	other threads:[~2009-10-19 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 17:02 Dmitry Eremin-Solenikov
2009-10-15 23:10 ` Doug Evans
2009-10-19 13:29   ` Dmitry Eremin-Solenikov [this message]
2009-10-19 17: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=4ADC6A35.4020709@gmail.com \
    --to=dbaryshkov@gmail.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@sebabeach.org \
    /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).