Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 25 Feb 2024 21:16:04 -0500
From: Rich Felker <>
To: "Venkata Ramanaiah Nalamothu (QUIC)" <>
Cc: "" <>
Subject: Re: RISC-V 32bit port in MUSL upstream

On Wed, Nov 08, 2023 at 03:00:09PM +0000, Venkata Ramanaiah Nalamothu (QUIC) wrote:
> Ping.

I believe this is actually close to ready-to-merge. I just pushed what
I think was the last missing prerequisite patch:

If the riscv32 port builds and works cleanly now with no further
changes to non-arch-specific code, I think it can be upstreamed now.
I'll try to take a look at this in the next couple days.


> -----Original Message-----
> From: Venkata Ramanaiah Nalamothu (QUIC) 
> Sent: Thursday, October 5, 2023 8:54 AM
> To:
> Subject: RE: [musl] RISC-V 32bit port in MUSL upstream
> Looks like that has changed and the ABI is being considered stable, otherwise GLIBC upstream wouldn't have accepted the RISC-V 32bit port, which is available since 2021 in GLIBC upstream.
> As per [1],
>      * 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.
> Regards,
> Ram Nalamothu
> [1]
> P.S: Apologies for the repost, the previous response was confusing because of the incorrect formatting.
> -----Original Message-----
> From: Markus Wichmann <> 
> Sent: Friday, September 29, 2023 8:13 PM
> To:
> Subject: Re: [musl] RISC-V 32bit port in MUSL upstream
> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
> Am Thu, Sep 28, 2023 at 04:39:37AM +0000 schrieb Venkata Ramanaiah Nalamothu (QUIC):
> > Thank you very much for sharing the patch set/development branch.
> >
> > Looking at your github tree commit history, it seems the tree is actively maintained.
> > May I know what is stopping from pushing these changes into MUSL community version?
> > Were there any technical challenges or someone just need to find time to work with the community to get the changes reviewed/merged?
> According to [0], main issue for Rich was that it was not a stable ABI yet back in 2020. Has that changed yet?
> Ciao,
> Markus
> [0]

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.