From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9513 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: [lowrisc-dev] musl risc-v port & gsoc - resources & ideas Date: Sun, 6 Mar 2016 13:45:21 -0500 Message-ID: <20160306184520.GU9349@brightrain.aerifal.cx> References: <20160304035811.GA10218@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1457289939 31613 80.91.229.3 (6 Mar 2016 18:45:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Mar 2016 18:45:39 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9526-gllmg-musl=m.gmane.org@lists.openwall.com Sun Mar 06 19:45:38 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1acdgP-0003kg-Fj for gllmg-musl@m.gmane.org; Sun, 06 Mar 2016 19:45:37 +0100 Original-Received: (qmail 3176 invoked by uid 550); 6 Mar 2016 18:45:35 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3158 invoked from network); 6 Mar 2016 18:45:34 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:9513 Archived-At: 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