From: Sergey Belyashov <sergey.belyashov@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Sergey Belyashov via Cgen <cgen@sourceware.org>
Subject: Re: BUG: non-fixed-length ISAs are unsupported for now
Date: Tue, 11 Aug 2020 18:57:12 +0300 [thread overview]
Message-ID: <CAOe0RDw6QWgRBRpiJ1Yr7scXrVPi-0z-DAFT8s8a+9RABh+S-A@mail.gmail.com> (raw)
In-Reply-To: <20200811153823.GA20457@redhat.com>
Hi,
Thank you for your response.
> .... these sound like they could fit into a single isa. You could
> have a family of ifields, one set for each of these prefix
> combinations. (Many could have different names and bit offsets but be
> otherwise the same.) Then for each instruction, you would have a set
> of separate define-instruction's for each prefix combination (!),
> using the corresponding ifields. Ideally, use a cgen macro to
> generate the separate define-instructions, to factor out the
> commonalities.
I have already tried to stay within one ISA but my attempt fails. You
may look here for full source of my try:
https://github.com/b-s-a/binutils-gdb/blob/z80-cgen/cpu/z80.cpu
(invalid decoder is generated for last 2 lines - "reti" (ED 4D) and
"retn" (ED 45) instructions, I have tried many types of ifields with
same result, but these are simpler to read). I cannot understand what
I'm doing wrong.
Best regards,
Sergey Belyashov
next prev parent reply other threads:[~2020-08-11 15:57 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
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 [this message]
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=CAOe0RDw6QWgRBRpiJ1Yr7scXrVPi-0z-DAFT8s8a+9RABh+S-A@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).