qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 22 Apr 2022 20:15:33 -0700	[thread overview]
Message-ID: <331420f7-9bc8-44b6-b9db-e1d82cfdd399@www.fastmail.com> (raw)
In-Reply-To: <CAMo8BfKPgZ29ReVE9CYmzfZ0sfem-fXqLf-2TW8qYQpO6fPA3g@mail.gmail.com>

Hi Max,

On Thu, Apr 21, 2022, at 1:56 PM, Max Filippov wrote:
> 
> An update to target/xtensa/cores.list is needed for this core to be built
> in qemu-6.2+. Please keep that file alphabetically sorted.

sounds great, thank you for the review!!! Will send out v2 soon.

> I'm curious how is it supposed to be used?

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). Given how it's one person's side project (mine), it's a lot closer to a (not-even-self-hosting) lispy-syntax lx106 assembler (... written in Common Lisp) at this point though.

Specifically, qemu is being used for testing code generation; within test cases, we generate an object file, link it up into an ELF image, launch it under qemu & check the output. Current top achievement: a loop that iterates 10 times and quits successfully, by using the emulated syscall interface. Even so, having actual test cases for this (& occasionally attaching gdb to them) is really useful.

(Admittedly, I can't really think of a lot of other use cases; probably everyone else is just using the official C toolchain?)

Simon




  reply	other threads:[~2022-04-23  7:58 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 [this message]
2022-04-23 21:26     ` Max Filippov
2022-04-25  5:40       ` Simon Safar via
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=331420f7-9bc8-44b6-b9db-e1d82cfdd399@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).