From: Sergey Belyashov <sergey.belyashov@gmail.com>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: Sergey Belyashov via Cgen <cgen@sourceware.org>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: BUG: non-fixed-length ISAs are unsupported for now
Date: Mon, 27 Apr 2020 22:34:34 +0300 [thread overview]
Message-ID: <CAOe0RDz3E99N8=5L7zW4srgMMAecWbFrfiqKQvEY63fuvXocGw@mail.gmail.com> (raw)
In-Reply-To: <87pnbsztze.fsf@gnu.org>
Ok, I understand.
I try to do next experiment:
set (base-insn-bitsize 24) in ISA definition (without it CGEN fails)
(dni retn "return from NMI handler" (all-isas UNCOND-CTI) "retn" (+
(f-0 #xED) (f-1 #x4500)) () ())
(dni reti "return from INT handler" (all-isas UNCOND-CTI) "reti" (+
(f-0 #xED) (f-1 #x4D00)) () ())
and now:
static const CGEN_IFMT ifmt_retn ATTRIBUTE_UNUSED = {
16, 16, 0xff, { { F (F_0) }, { F (F_1) }, { 0 } }
};
/* retn */
{
{ 0, 0, 0, 0 },
{ { MNEM, 0 } },
& ifmt_retn, { 0x45ed }
},
/* reti */
{
{ 0, 0, 0, 0 },
{ { MNEM, 0 } },
& ifmt_retn, { 0x4ded }
},
code looks more correct, but it does not work properly.
пн, 27 апр. 2020 г. в 21:03, Jose E. Marchesi <jemarch@gnu.org>:
>
> 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).
>
> Then your base-insn-bitsize should be 8.
>
> The key here is: how are opcodes expressed in your ISA? Do they appear
> in the first base insn only, or they are scattered in the optional bytes
> in long instructions?
>
> CGEN currently has two limitations in its implementation:
> 1) It does not support having opcodes (i.e. entries of the form (f-FOO
> VAL) in (+ ) field descriptions) past the first 64 bits of an
> instruction.
> 2) It does not support to have opcode fields placed in their own word.
>
> These limitations have bitten me in the BPF port and, at the moment, I
> have a couple of workarounds in place, but it would be nice to remove
> them.
>
> For an example of an instruction set with variable length instructions
> see cpu/ia32.cpu in the CGEN distribution for an example of
> variable-length instruction set. However, the "FIXME" annotations in
> instructions that (f-reg/opcode 0) are most probably there because that
> opcode field is not applied properly, since it is defined to be in the
> second word of the instruction (limitation (2) above.)
>
next prev parent reply other threads:[~2020-04-27 19:34 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
2020-04-27 18:03 ` Jose E. Marchesi
2020-04-27 19:34 ` Sergey Belyashov [this message]
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='CAOe0RDz3E99N8=5L7zW4srgMMAecWbFrfiqKQvEY63fuvXocGw@mail.gmail.com' \
--to=sergey.belyashov@gmail.com \
--cc=cgen@sourceware.org \
--cc=fche@redhat.com \
--cc=jemarch@gnu.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).