From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9459 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general,gmane.comp.hardware.lowrisc.devel Subject: Re: Interest in "Porting musl libc to RISC-V" project for GSoC 2016 Date: Thu, 3 Mar 2016 22:02:26 -0500 Message-ID: <20160304030226.GA9349@brightrain.aerifal.cx> References: <20160303220641.GL29662@port70.net> 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 1457060566 16144 80.91.229.3 (4 Mar 2016 03:02:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Mar 2016 03:02:46 +0000 (UTC) Cc: musl@lists.openwall.com, lowrisc-dev@lists.lowrisc.org To: Masanori Ogino Original-X-From: musl-return-9472-gllmg-musl=m.gmane.org@lists.openwall.com Fri Mar 04 04:02:45 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 1abg0q-0002Y0-6a for gllmg-musl@m.gmane.org; Fri, 04 Mar 2016 04:02:44 +0100 Original-Received: (qmail 16093 invoked by uid 550); 4 Mar 2016 03:02:41 -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 16072 invoked from network); 4 Mar 2016 03:02:40 -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:9459 gmane.comp.hardware.lowrisc.devel:297 Archived-At: On Fri, Mar 04, 2016 at 09:54:44AM +0900, Masanori Ogino wrote: > Hello, > > 2016-03-04 7:06 GMT+09:00 Szabolcs Nagy : > > last time iirc musl port was considered to be > > not large enough in itself for a gsoc project > > (i think it should not take more than 2 months > > but i don't know the current state of risc-v > > qemu/linux/gcc/etc) > > > > you might need to think additional things to work on. > > > > for musl, one idea is to invest extra time on testing. > > > > for risc-v i think polishing the toolchain and the docs > > would be useful. > > Agreed. > > > there are some basic problems with the risc-v software > > eco-system: > > > > there is no proper sysv psabi spec. (designing one would > > have been better than copying obsolete nonsense from mips > > as i can see in the glibc port.) > > Hmm, ABI is an important factor for the proposal, but I probably won't > have enough time to invent a new ABI and implement it during this > summer... > Anyway, would you give me any well-designed psABI (or non-SysV-psABI) examples? I don't think you'd need to change/redesign the ABI (since it's already being used on FreeBSD, presumably whatever current Linux kernel port exists, and maybe other targets, and didn't look bad when I looked at it), but a nice clean psABI document would be nice to have. > > nothing is upstream yet (gcc/linux/.. ports are > > maintained out of tree, working with the upstream > > community is important for many reasons). > > Agreed with the importance of merging to upstream. > > > risc-v mailing lists are not public, only subscribers > > can see or participate in the discussions. (this is > > bad given that there are no specs, no upstreamed code > > so no source of information for outsiders.) > > I think it would be great if archives are public. I don't know the > reason why the project decide to do so. Yes, that would be really nice. > > for a musl port this means that we don't have abi > > stability guarantees, the port can stop working with > > the rest of the risc-v software stack. so for a > > successful port i think some scripts should be developed > > to build and test the latest risc-v things against musl > > (cross-toolchain, rootfs, etc) so we can keep it working. > > Indeed it's great to have an automated testing infrastructure. I really love CI. > > Thank you for your suggestion! I have a few other ideas I'm going to post to the list for elements that could be incorporated into proposals. I'll follow up as a separate email. Rich