diff options
author | Ben Hutchings <ben@decadent.org.uk> | 2023-02-12 19:46:35 +0100 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2023-02-12 19:46:35 +0100 |
commit | 81c93ed662cd8b3f38871bc002582f5abee9b99f (patch) | |
tree | 2ab7f4894fbc7dc4a03230ba7738fb95a160d513 | |
parent | a640efa79ef73b5c2943c42abc027f78fadf57b9 (diff) | |
download | klibc-maint-81c93ed662cd8b3f38871bc002582f5abee9b99f.tar.gz |
status.md: Add results with QEMU 7.2
QEMU 7.2 has some regressions, but earlier versions don't emulate the
time64 system calls for 32-bit architectures.
-rw-r--r-- | status.md | 20 |
1 files changed, 20 insertions, 0 deletions
@@ -15,6 +15,8 @@ test-many-klibcs implements: ### 2.0.10 +With patched QEMU 3.1: + * arm, i386, m68k, parisc, ppc, sh: * Fail to build (with Linux 5.19 headers) * arm64: @@ -32,6 +34,8 @@ test-many-klibcs implements: ### 2.0.11, 2.0.12 +With patched QEMU 3.1: + * mipsisa64r6, mipsisa64r6el: * Linker error "relocation truncated to fit: R_MIPS_PC26_S2" when building a shared executable with gcc @@ -46,6 +50,19 @@ test-many-klibcs implements: * sh4: * All executables hang when built with gcc 12 +With QEMU 7.2: + +* armhf: + * All tests fail (SIGSEGV) in shared build. Seems to be a QEMU bug. +* mipsisa64r6, mipsisa64r6el: + * Linker error "relocation truncated to fit: R_MIPS_PC26_S2" when + building a shared executable with gcc +* riscv64: + * All tests fail in shared build. Seems to be a QEMU bug. + * 2a:sigint: Fails when built with Clang +* sh4: + * All executables hang when built with gcc 12 + ### Known bugs elsewhere QEMU 3.1 had a bug in handling of struct timveval on sparc64, and a @@ -56,6 +73,9 @@ build, qemu-user-static_3.1+dfsg-2.1_amd64.deb. QEMU 6.1 fixes those plus the s390x failures, but also has regressions for armhf, hppa, and riscv64. +QEMU 7.2 fixes hppa, but still has regressions for armhf and riscv64. +But we need it for time64 support. + Clang 13 has a bug that affects i386, -mregparm, and optimisation of printf() to puts(). The call to puts() passes arguments using the usual stack-based calling convention. This is now worked-around |