public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alistair Francis <alistair23@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/alistair/rv32.next] COVER: glibc port for 32-bit RISC-V (RV32) Date: Wed, 22 Apr 2020 22:16:45 +0000 (GMT) [thread overview] Message-ID: <20200422221645.A818939551C5@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=24bf5aaf8b2d2cef8a8a33c3783e7867a86fe278 commit 24bf5aaf8b2d2cef8a8a33c3783e7867a86fe278 Author: Alistair Francis <alistair.francis@wdc.com> Date: Mon Dec 30 13:33:07 2019 -0800 COVER: glibc port for 32-bit RISC-V (RV32) This patch set contains the glibc port for 32-bit RISC-V. This is based on the original work from Zong Li [1] and has been updated to use a 64-bit time_t. This requires a 5.4+ kernel and all of the testing has been done using the 5.4 stable kernel. Nothing fails when running ./scripts/build-many-glibcs.py (for all targets) on my x86-64 machine. This is the current list of tests that fail when running inside QEMU RV32 system emulation on the 5.4 kernel: FAIL: elf/tst-ldconfig-ld_so_conf-update FAIL: io/tst-lockf FAIL: misc/test-errno-linux FAIL: nss/tst-nss-files-hosts-long FAIL: resolv/tst-resolv-res_init-thread FAIL: stdio-common/bug22 FAIL: stdlib/tst-strfrom FAIL: stdlib/tst-strfrom-locale FAIL: sysvipc/test-sysvmsg ---Links--- 1: https://sourceware.org/ml/libc-alpha/2018-07/msg00892.html The latest version of my work can be found here: https://github.com/alistair23/glibc/tree/alistair/rv32.next This specific version can be found here: https://github.com/alistair23/glibc/tree/alistair/rv32.1 ---Changelog--- v1: - Update based from feedback on RFCv6 - Improve test passing - There are only 9 tests failing now - Rebase on Lukasz's work - Send only the RV32 specific patches (other patches are already merged or on the list) RFC v6: - Rebase on top of accetpted patches - Fix issues so that the tests actually run RFC v5: - Hopefully finally get the correct layout for the *64 syscalls - Sort out the Changelog RFC v4: - Continue to fix things that weren't working - Update the coding style to match glibc - Update the __ASSUME_TIME64_SYSCALLS work to better match Lukasz's work RFC v3: - Remove all "Hack" patches - Incorporate upstream comments - Ensure we don't break RV64 - Lot's more testing and fixes RFC v2: - Add Lukasz's patches - Update the non HACK syscalls after feedback - define __ASSUME_TIME64_SYSCALLS and __ASSUME_RLIM64_SYSCALLS - Remove lockf64.c - Other smaller changes from RFC v1 Diff: --- __COVER__ | 0 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/__COVER__ b/__COVER__ new file mode 100644 index 0000000000..e69de29bb2
next reply other threads:[~2020-04-22 22:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-22 22:16 Alistair Francis [this message] 2020-04-26 2:26 Alistair Francis
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=20200422221645.A818939551C5@sourceware.org \ --to=alistair23@sourceware.org \ --cc=glibc-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).