From: David Gibson <david@gibson.dropbear.id.au>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Sergio Lopez" <slp@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>, QEMU <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
hreitz@redhat.com,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Rust in Qemu BoF followup: Rust vs. qemu platform support
Date: Mon, 20 Sep 2021 13:41:36 +1000 [thread overview]
Message-ID: <YUgC8HThCulgUFcB@yekko> (raw)
In-Reply-To: <dc2df310-ee28-a912-3aad-4d3e38974182@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
On Sat, Sep 18, 2021 at 01:01:35PM -0700, Richard Henderson wrote:
> On 9/17/21 4:03 AM, David Gibson wrote:
> > > For sparc 32, it was added to support Gentoo at that time which didn't
> > > switch to 64-bit yet (https://github.com/rust-lang/rust/pull/48297)
> > >
> > > For the past 2-3y, Gentoo sparc is now 64 bit. (like Debian apparently for
> > > a while)
> > >
> > > But apparently, by lack of CI it was downgraded to Tier-3.
> > >
> > > Is it reasonable to officially drop support for sparc 32 in QEMU
> > > too?
> >
> > As a qemu build arch I would say probably yes.
>
> We dropped host support for sparcv8 (true 32-bit) a long time ago.
> We only support sparcv9 in ilp32 (sparcv8plus) and lp64 (sparc64).
We really need to update
https://qemu-project.gitlab.io/qemu/about/build-platforms.html
to clarify this then. I don't really know what the procedures are for
updating the website.
> I'd be happy top drop sparcv8plus as well, because I haven't been able to
> test it for something like 2-3 years.
Sounds like a reasonable reason.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-20 5:09 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
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 [this message]
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=YUgC8HThCulgUFcB@yekko \
--to=david@gibson.dropbear.id.au \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=hreitz@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).