From: "Simon Safar" via <qemu-devel@nongnu.org>
To: "Max Filippov" <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] target/xtensa: import core lx106
Date: Sun, 24 Apr 2022 22:40:17 -0700 [thread overview]
Message-ID: <b24c44b0-4cc0-4165-b794-44f1c61e3460@www.fastmail.com> (raw)
In-Reply-To: <CAMo8Bf+6gg4w1D_V8GBmePhC0Opf08Ctp3G90QpO69Yfk87B8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Sat, Apr 23, 2022, at 2:26 PM, Max Filippov wrote:
> > It's for a (future...) Lisp compiler! Somewhat in the style of MicroPython; the idea
> > is to make code editable on the fly, without reflashing (... or restarting, even).
>
> Interesting. Do you use libisa or do you do instruction encoding on your own?
It's my own; it's generating opcodes from the tree of tables in the Xtensa reference. A large part of the actual code looks a lot like those tables themselves; there are still some missing parts for some (e.g. overriding some defaults on which instruction is taking what kinds of parameters), which I'm just filling in on the go. It's fairly hacky, but it might fit together well with the eventual purpose of maybe running some of this in that 40k RAM onboard & keeping it all Lisp.
(I'll put it up somewhere eventually once it's not a complete mess & starts doing something interesting! assuming this ever happens, of course.)
Simon
[-- Attachment #2: Type: text/html, Size: 1353 bytes --]
next prev parent reply other threads:[~2022-04-25 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 15:57 [PATCH] target/xtensa: import core lx106 Simon Safar via
2022-04-21 20:56 ` Max Filippov
2022-04-23 3:15 ` Simon Safar via
2022-04-23 21:26 ` Max Filippov
2022-04-25 5:40 ` Simon Safar via [this message]
2022-04-25 14:08 ` Max Filippov
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=b24c44b0-4cc0-4165-b794-44f1c61e3460@www.fastmail.com \
--to=qemu-devel@nongnu.org \
--cc=jcmvbkbc@gmail.com \
--cc=simon@simonsafar.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 NNTP newsgroup(s).