From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [lowrisc-dev] musl risc-v port & gsoc - resources & ideas
Date: Sun, 6 Mar 2016 13:45:21 -0500 [thread overview]
Message-ID: <20160306184520.GU9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <CA+wsVCDbvOnMaYrtBYJ2EnvKiK2YZPcp_YMiBsb-9EADGFQhBQ@mail.gmail.com>
On Sun, Mar 06, 2016 at 06:31:30PM +0000, Hesham Almatary wrote:
> Hi Rich,
>
> Thanks for this detailed e-mail. It's worth mentioning that during my
> last GSoC project that ported seL4 to RISC-V, I had to add RISC-V
> support to the muslc library [1] (only 32-bit, imitating the or1k
> port). It was mainly useful for userspace tasks, and works pretty
> well.
>
> I thought this might be a good starting point for anyone who might
> work on this project. We can work to get this local code upstream if
> that makes sense.
>
> [1] https://github.com/heshamelmatary/musllibc
Thanks for letting us know. Another student who's interested in the
project also just contacted me and has a partially-finished port that
was done independently. So I think a viable GSoC proposal for this is
going to need to go well beyond the initial porting work and aim to
get riscv support to first-class status. That probably means putting a
strong focus on testing, finding performance bottlenecks (which
doesn't necessarily mean writing asm to fix them; rather it might be
identifying and reporting compiler bugs that are causing the compiler
to generate bad code for the C), etc.
Now would be a good time for students interested in the project to
jump in with ideas.
Rich
next prev parent reply other threads:[~2016-03-06 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 3:58 Rich Felker
2016-03-06 3:25 ` Rich Felker
2016-03-06 18:31 ` Hesham Almatary
2016-03-06 18:45 ` Rich Felker [this message]
2016-03-06 22:33 ` 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=20160306184520.GU9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).