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] Documentation for the RISC-V 32-bit port Date: Thu, 27 Aug 2020 18:37:51 +0000 (GMT) [thread overview] Message-ID: <20200827183751.1233B3894C36@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=389f6854eb43d892cca69f8b3bfaf813e0516127 commit 389f6854eb43d892cca69f8b3bfaf813e0516127 Author: Alistair Francis <alistair.francis@wdc.com> Date: Tue Jul 14 06:29:56 2020 -0700 Documentation for the RISC-V 32-bit port There is already RISC-V 64-bit port information in the documentation. Let's add some documentation entries for the RISC-V 32-bit as well. Reviewed-by: Maciej W. Rozycki <macro@wdc.com> Diff: --- NEWS | 11 ++++++++++- README | 1 + 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 2937adc3f3..06e43e0453 100644 --- a/NEWS +++ b/NEWS @@ -9,7 +9,16 @@ Version 2.33 Major new features: - [Add new features here] + +* Support for the RISC-V ISA running on Linux has been expanded to run on + 32-bit hardware. This is supported for the following ISA and ABI pairs: + + - rv32imac ilp32 + - rv32imafdc ilp32 + - rv32imafdc ilp32d + + The 32-bit RISC-V port requires at least Linux 5.4, GCC 7.1 and binutils + 2.28. Deprecated and removed features, and other changes affecting compatibility: diff --git a/README b/README index 903f07e484..d0f0edb393 100644 --- a/README +++ b/README @@ -39,6 +39,7 @@ The GNU C Library supports these configurations for using Linux kernels: powerpc64*-*-linux-gnu Big-endian and little-endian. s390-*-linux-gnu s390x-*-linux-gnu + riscv32-*-linux-gnu riscv64-*-linux-gnu sh[34]-*-linux-gnu sparc*-*-linux-gnu
reply other threads:[~2020-08-27 18:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200827183751.1233B3894C36@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).