qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	devel@lists.libvirt.org, "Artyom Tarasenko" <atar4qemu@gmail.com>
Subject: Re: [RFC PATCH 6/6] docs/about: deprecate add sparc/sparc32plus-*-user
Date: Wed, 16 Jul 2025 13:02:25 +0200	[thread overview]
Message-ID: <381ee2b8-a6ab-4770-aeb6-c1e83d2478ef@redhat.com> (raw)
In-Reply-To: <20250716105414.2330204-7-alex.bennee@linaro.org>

On 16/07/2025 12.54, Alex Bennée wrote:
> Even with a toolchain *-user is still broken. Maybe we should just
> deprecate the target. I haven't deprecated for system as we have
> functional tests that work and will continue to do so.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
>   docs/about/deprecated.rst | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index d50645a071..c2199129d8 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -267,6 +267,14 @@ known-good implementation to test against. GCC is in the process of
>   dropping their support for iwMMXt codegen. These CPU types are
>   therefore deprecated in QEMU, and will be removed in a future release.
>   
> +``sparc`` and ``sparc32plus`` (since 10.1)
> +''''''''''''''''''''''''''''''''''''''''''
> +
> +Without regular testing these targets have bit-rotted and even after
> +scrapping together the seemingly last packaged toolchain we can't
> +generate binaries that can currently be run.

I think it's fair to deprecate it in this case. If someone wants to maintain 
it, they can come up with patches and we can revert this patch. Otherwise 
it's only dead code anyway.

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2025-07-16 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 10:54 [RFC PATCH 0/6] Fix building of sparc/sparc32plus test cases Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 1/6] tests/tcg: special case sparc " Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 2/6] tests/tcg: special case sparc32plus " Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 3/6] configure: update sparc and sparc32plus target compiler detection Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 4/6] tests/docker: add sparc-leon-cross container image Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 5/6] configure: enable the container fallbacks for sparc/sparc32plus Alex Bennée
2025-07-16 10:54 ` [RFC PATCH 6/6] docs/about: deprecate add sparc/sparc32plus-*-user Alex Bennée
2025-07-16 11:02   ` Thomas Huth [this message]
2025-07-17 12:32 ` [RFC PATCH 0/6] Fix building of sparc/sparc32plus test cases Mark Cave-Ayland
2025-07-17 13:51   ` Alex Bennée
2025-07-17 15:10   ` Richard Henderson
2025-07-21 19:52 ` Mark Cave-Ayland

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=381ee2b8-a6ab-4770-aeb6-c1e83d2478ef@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=atar4qemu@gmail.com \
    --cc=devel@lists.libvirt.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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 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).