From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RDNS_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 Received: (qmail 9330 invoked from network); 12 Mar 2020 13:57:30 -0000 Received-SPF: pass (mother.openwall.net: domain of lists.openwall.com designates 195.42.179.200 as permitted sender) receiver=inbox.vuxu.org; client-ip=195.42.179.200 envelope-from= Received: from unknown (HELO mother.openwall.net) (195.42.179.200) by inbox.vuxu.org with ESMTP; 12 Mar 2020 13:57:30 -0000 Received: (qmail 17666 invoked by uid 550); 12 Mar 2020 13:57:28 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17645 invoked from network); 12 Mar 2020 13:57:27 -0000 Date: Thu, 12 Mar 2020 09:57:15 -0400 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200312135715.GK11469@brightrain.aerifal.cx> References: <7D9266CBFB4E9A4B9C7B1D0341567D8601727F45@DGGEMI529-MBX.china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7D9266CBFB4E9A4B9C7B1D0341567D8601727F45@DGGEMI529-MBX.china.huawei.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] musl support riscv32 On Thu, Mar 12, 2020 at 11:09:37AM +0000, chengzhiwei (C) wrote: > Hi, all: > Recently, we did a survey about musl lib supported by the target of riscv. As we know, musl-riscv64 was released last year, it's a great job: > https://git.musl-libc.org/cgit/musl/commit/?id=0a48860c27a8eb291bcc7616ea9eb073dc660cab > > But we want to know when musl will suoport riscv-32 target and be released in the community based on the latest version? > From the community, we found that the previous branch version supported 32 bits backend, > https://github.com/riscv/riscv-musl/tree/riscv-musl-1.1.18 > https://github.com/riscv/riscv-musl/tree/riscv-musl-1.1.20 > I guess there are still lots of tests to be done for stability reasons. Next release can support riscv-32 target? > > Maybe it's not an easy job about atomic operation. If the version support date is uncertain, can you share some solutions to circumvent it? > Our team is also considering the possibility of implementing the functionality in C code, could you give us some suggestions? > > Hope your responseļ¼ The main blocker for riscv32 has been that the kernel has not declared it a stable ABI yet. At the time it was first proposed, there were still problems related to it being a 32-bit arch with no legacy 32-bit time_t syscalls, but that's not an issue now. I'd be happy to look at an updated riscv32 port now (ideally based on what's upstram in musl for riscv64, converted to 32-bit, rather than the old proposal, since lots of bugs were fixed after it was merged) and hopefully convince Linus/kernel ppl to consider it stabilized on the basis that there's a libc ready to use it. Rich