On 7/29/22 14:21, Richard Henderson wrote:
This is, technically, a regression from 6.2, so it's not implausible to apply before rc1. Thoughts?
In gitlab #1097 the author comments that: https://gitlab.com/qemu-project/qemu/-/issues/1097#note_1044810483 "there are several distributions still available on 32-bit powerpc, e.g. Adélie Linux, for now still Void Linux, afaik Debian and OpenSUSE also still build packages" I checked these claims. Latest version OpenSuse LEAP doesn't support ppc32 bits: https://get.opensuse.org/leap/15.4/#download The last Debian that supports ppc32 was Debian 8: https://www.debian.org/ports/powerpc/#powerpc "Debian on 32-bit PowerPC (powerpc) It first became an official release architecture with Debian GNU/Linux 2.2 (potato) and had retained that status until the publication of Debian 9 (stretch). The last supported release for 32-bit PowerPC is Debian 8 (jessie)" And Void Linux doesn't seem to support any PowerPC flavor: https://voidlinux.org/download/ Adélie Linux supports ppc32. I can also add that FreeBSD also supports ppc32. Checking about/build-platforms.rst I can see that we would only somewhat care for FreeBSD here, since Debian 8 is already out of our support window. All that said, I don't have strong feelings against re-enabling it, specially because this build issue was deliberated caused by us. However, after re-enabling it, I would only care about build bugs that are reproduced on ppc32 FreeBSD. Daniel
r~ Richard Henderson (2): common-user/host/ppc: Implement safe-syscall.inc.S linux-user: Implment host/ppc/host-signal.h linux-user/include/host/ppc/host-signal.h | 39 ++++++++ common-user/host/ppc/safe-syscall.inc.S | 107 ++++++++++++++++++++++ 2 files changed, 146 insertions(+) create mode 100644 linux-user/include/host/ppc/host-signal.h create mode 100644 common-user/host/ppc/safe-syscall.inc.S
