From: Cornelia Huck <cohuck@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, slp@redhat.com, f4bug@amsat.org,
hreitz@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
marcandre.lureau@redhat.com, alex.bennee@linaro.org,
sgarzare@redhat.com
Subject: Re: Rust in Qemu BoF followup: Rust vs. qemu platform support
Date: Fri, 17 Sep 2021 11:17:01 +0200 [thread overview]
Message-ID: <87k0jfh88i.fsf@redhat.com> (raw)
In-Reply-To: <YURYvaOpya498Xx2@yekko>
On Fri, Sep 17 2021, David Gibson <david@gibson.dropbear.id.au> wrote:
> Hi all,
>
> At the qemu-in-rust BoF at KVM Forum, I volunteered to look into
> whether Rust supported all the host/build platforms that qemu does,
> which is obviously vital if we want to make Rust a non-optional
> component of the build.
>
> I've added the information to our wiki at:
> https://wiki.qemu.org/RustInQemu
Thank you for doing that!
>
> TBH, the coverage is not as good as I expected. Linux, macOS and
> Windows are pretty much ok, with the exception of Linux on Sparc.
> There are a lot of gaps in *BSD support, however.
Yes :(
Do we actually have an idea what we would require? I'm surprised that
there are so many targets without host tools or without std support (but
maybe they are only missing small things.)
>
> I've included some notes on where the information comes from, and some
> uncertainties in there.
>
> I've made an effort to get the information correct, but double
> checking would be appreciated.
I did not spot any errors on a quick cross check, but I'm not really
sure about what the BSDs support.
>
> I haven't yet looked into the packaging situation for the Rust
> toolchain on various platforms and distros, but I still intend to do
> so.
next prev parent reply other threads:[~2021-09-17 9:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 8:58 Rust in Qemu BoF followup: Rust vs. qemu platform support David Gibson
2021-09-17 9:17 ` Cornelia Huck [this message]
2021-09-17 9:54 ` Marc-André Lureau
2021-09-17 11:03 ` David Gibson
2021-09-18 20:01 ` Richard Henderson
2021-09-20 3:41 ` David Gibson
2021-09-20 8:13 ` Peter Maydell
2021-09-21 5:57 ` David Gibson
2021-09-17 10:56 ` David Gibson
2021-09-17 11:11 ` Philippe Mathieu-Daudé
2021-09-17 15:56 ` Stefan Hajnoczi
2021-09-18 5:25 ` David Gibson
2021-09-17 11:34 ` Daniel P. Berrangé
2021-09-17 15:59 ` Stefan Hajnoczi
2021-09-18 5:28 ` David Gibson
2021-09-17 16:04 ` Warner Losh
2021-09-17 18:39 ` Philippe Mathieu-Daudé
2021-09-17 19:02 ` Warner Losh
2021-09-20 3:53 ` David Gibson
2021-09-20 13:58 ` Ed Maste
2021-09-20 3:43 ` David Gibson
2021-09-20 2:23 ` Brad Smith
2021-09-20 4:07 ` David Gibson
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=87k0jfh88i.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=hreitz@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@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 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.