mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "chengzhiwei (C)" <chengzhiwei6@huawei.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: [musl] musl support riscv32
Date: Thu, 12 Mar 2020 11:09:37 +0000	[thread overview]
Message-ID: <7D9266CBFB4E9A4B9C7B1D0341567D8601727F45@DGGEMI529-MBX.china.huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

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!

All the best,
--zhiwei


[-- Attachment #2: Type: text/html, Size: 4363 bytes --]

             reply	other threads:[~2020-03-12 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 11:09 chengzhiwei (C) [this message]
2020-03-12 13:57 ` Rich Felker
2020-03-13  2:05   ` [musl] 答复: " chengzhiwei (C)
2020-03-13  2:13     ` Rich Felker
     [not found]   ` <202003130543.02D5h9Zk085624@ATCSQR.andestech.com>
2020-03-13  6:02     ` Ruinland ChuanTzu Tsai
2020-03-13 14:05       ` Rich Felker

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=7D9266CBFB4E9A4B9C7B1D0341567D8601727F45@DGGEMI529-MBX.china.huawei.com \
    --to=chengzhiwei6@huawei.com \
    --cc=musl@lists.openwall.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).