From 6a83c7b176ff0ffc920a9fc219aa637ab9aa0036 Mon Sep 17 00:00:00 2001 From: Samuel Thibault <samuel.thibault@ens-lyon.org> Date: Wed, 5 Feb 2025 19:00:08 +0100 Subject: contributing: Actually the python testsuite issues on hurd-amd64 appear on hurd-i386 too --- contributing.mdwn | 1 - 1 file changed, 1 deletion(-) diff --git a/contributing.mdwn b/contributing.mdwn index 98817e3d..7f4f3554 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -164,7 +164,6 @@ This is the list of tasks that we *want* to address soon, starting with the most * Fix shell output pipe replacement issue on amd64, see [discussion](https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00062.html). - This means adding an `i386x_float_state` and `i386_XFLOAT_STATE` thread status, that glibc would be able to use along `i386_REGS_SEGS_STATE` and `i386_FLOAT_STATE` in `_hurd_setup_sighandler` and `sigtreturn.c`. The structure would contain the `fp_save_kind`. That'll actually be needed both on `i386` and `x86_64` actually, to fix SSE use against signals in general. -* Compare testsuite results of python on hurd-i386 and hurd-amd64, to fix regressions between the former and the latter. * Check the [packages build failures differences](https://people.debian.org/~sthibault/hurd-amd64/failed_diff.txt) between hurd-i386 and hurd-amd64: they are failing on hurd-amd64 but are successful on hurd-i386. Possibly it's just a mere missing `s/hurd-i386/hurd-any/` in the debian/ directory, or a new bug that actually also affects hurd-i386 if you rebuild the package there now, but possibly it's a more profound issue in the amd64 port. * On amd64, fix memcpy (> 16 bytes) from `/dev/mem` (makes hurd-console crash) * On amd64, fix crash-core -- cgit v1.2.3