From: Sergey Belyashov <sergey.belyashov@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org
Subject: Re: BUG: non-fixed-length ISAs are unsupported for now
Date: Mon, 27 Apr 2020 20:52:11 +0300 [thread overview]
Message-ID: <CAOe0RDxY-ZOavy6xJo+3nGOeCXc3_tiPAQrZbzBfzHc3wARcNQ@mail.gmail.com> (raw)
In-Reply-To: <CAOe0RDx2ppy3fqVTyWpEaVpXK-PvKeJNMEc4tKtPhqtKcmdUCA@mail.gmail.com>
I have tried to increase base-insn-bitsize to 32, but nothing is
changed. z80_cgen_insn_opcode_table in z80-opc.c contains sum of
instruction bytes: 0xED 0x45 -> 0x132
Best regards,
Sergey Belyashov
пн, 27 апр. 2020 г. в 20:00, Sergey Belyashov <sergey.belyashov@gmail.com>:
> Hi,
> Z80 has istructions from 1 byte (nop for example) up to 4 bytes long (eZ80
> up to 6 bytes) including operands 0..2 bytes (eZ80 0..3 bytes). So
> base-insn-bitsize is set to 8. And it is not enought for 1-3 bytes (eZ80
> 1-4) insn code size (w/o immediate operands).
>
> Best regards,
> Sergey Belyashov
>
>
> пн, 27 апр. 2020 г., 19:29 Frank Ch. Eigler <fche@redhat.com>:
>
>> Hi -
>>
>> > While analyzing code of CGEN I have found next code:
>> > [...]
>> > Can anybody add support for non-fixed-length ISAs?
>>
>> I am not expecting major cgen improvements. However, if your
>> base-insn-size is large enough to contain all the opcode-like
>> bits of your largest possible instruction, you may not need
>> those improvements.
>>
>> - FChE
>>
>>
next prev parent reply other threads:[~2020-04-27 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 13:37 Sergey Belyashov
2020-04-27 16:29 ` Frank Ch. Eigler
2020-04-27 17:00 ` Sergey Belyashov
2020-04-27 17:52 ` Sergey Belyashov [this message]
2020-04-27 18:03 ` Jose E. Marchesi
2020-04-27 19:34 ` Sergey Belyashov
2020-04-27 20:01 ` Jose E. Marchesi
2020-04-27 20:23 ` Sergey Belyashov
2020-04-29 19:11 ` Sergey Belyashov
2020-07-30 9:11 ` Sergey Belyashov
2020-08-11 15:38 ` Frank Ch. Eigler
2020-08-11 15:57 ` Sergey Belyashov
2020-08-11 16:08 ` Frank Ch. Eigler
2020-08-12 13:59 ` Sergey Belyashov
2020-08-12 18:36 ` Frank Ch. Eigler
2020-08-12 18:53 ` Jose E. Marchesi
2020-08-12 19:19 ` Sergey Belyashov
2020-08-12 19:21 ` Frank Ch. Eigler
2020-08-12 19:27 ` Jose E. Marchesi
2020-08-12 19:44 ` Sergey Belyashov
2020-08-12 19:57 ` Frank Ch. Eigler
2020-08-13 13:34 ` Sergey Belyashov
2020-08-13 14:32 ` Frank Ch. Eigler
2020-08-13 14:47 ` Sergey Belyashov
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=CAOe0RDxY-ZOavy6xJo+3nGOeCXc3_tiPAQrZbzBfzHc3wARcNQ@mail.gmail.com \
--to=sergey.belyashov@gmail.com \
--cc=cgen@sourceware.org \
--cc=fche@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).