From: Keith Packard via <qemu-devel@nongnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Chris Wulff <crwulff@gmail.com>,
Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] target/nios2: Pass semihosting arg to exit
Date: Tue, 01 Aug 2023 08:28:43 -0700 [thread overview]
Message-ID: <87o7jqok7o.fsf@keithp.com> (raw)
In-Reply-To: <CAFEAcA-WHHn0-PfJ8vTgZL5xjvR+=n1_We3v7uRT+Phi6DzsMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
> Yeah, the closest to a "standard" we have for nios2 is that
> I asked the Codesourcery folks to document it in the libgloss
> sources and put the URL to it in a comment at the top of
> nios2-semi.c, given that there's no official spec and the
> original and main guest-side user is libgloss.
> m68k is in a similar position only without the URL
> in our source file :-)
Yeah, we had the same ask when getting risc-v semihosting merged. For
that, I actually pushed through an "official" risc-v standard. I kinda
wish I'd used the m68k model instead of the arm model as that provides
simple POSIX semantics...
https://github.com/riscv-software-src/riscv-semihosting/blob/main/riscv-semihosting-spec.adoc
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-08-01 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 22:41 [PATCH] target/nios2: Pass semihosting arg to exit Keith Packard via
2023-08-01 12:04 ` Peter Maydell
2023-08-01 15:10 ` Keith Packard via
2023-08-01 15:17 ` Peter Maydell
2023-08-01 15:28 ` Keith Packard via [this message]
2023-08-01 15:33 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 15:22 Keith Packard via
2023-08-01 15:24 ` Peter Maydell
2023-08-01 21:45 ` Philippe Mathieu-Daudé
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=87o7jqok7o.fsf@keithp.com \
--to=qemu-devel@nongnu.org \
--cc=crwulff@gmail.com \
--cc=keithp@keithp.com \
--cc=marex@denx.de \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.