From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: lowrisc-dev@lists.lowrisc.org
Subject: Re: musl risc-v port & gsoc - resources & ideas
Date: Sun, 6 Mar 2016 17:33:28 -0500 [thread overview]
Message-ID: <20160306223327.GW9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160304035811.GA10218@brightrain.aerifal.cx>
On Thu, Mar 03, 2016 at 10:58:12PM -0500, Rich Felker wrote:
> Since a port of musl to a new arch does not actually involve much
> code, mainly attention to detail to make sure that all of the type
> definitions/ABI/etc. are correct, I think that for a proposal to be
> big enough to make a reasonable GSoC project, it should go beyond just
> the basic porting. Some ideas for things to include would be:
>
> - Improvement of porting documentation
>
> - Feedback/patches on where there's too much redundancy between ports
> and how to reduce it (i.e. making improvements to musl that reduce
> the amount of code/headers needed for a new port).
>
> - Patches for musl-cross and/or musl-cross-make (build systems for
> generating a cross-compiler toolchain) to make it easy to build a
> musl/riscv cross compiler.
>
> - Optimizing performance-critical code like memcpy or floating point
> math functions for riscv.
>
> - Improving test coverage, especially for things that are easy to get
> wrong in a new port.
>
> I'll follow up with more ideas if I think of any.
>
> Students interested in the project are welcome (and encouraged!) to
> ask questions and discuss here on the musl list. Obviously everyone
> should have in mind writing their own proposals but I want everyone to
> have access to knowledge/resources/community for ideas.
One other thing I forgot: I believe the riscv ABIs use IEEE quad for
long double, but musl has very poor support for quad right now, Most
functions just call out to the double functions; only a few that
critically need to be exact actually do the right thing. Improving
this situation is important for making riscv and other archs (aarch64,
mips64) that use quad polished/first-class.
Also the lowrisc-dev cc seems to have gotten dropped on these emails
which are very relevant:
http://www.openwall.com/lists/musl/2016/03/06/17
http://www.openwall.com/lists/musl/2016/03/06/24
http://www.openwall.com/lists/musl/2016/03/06/25
Rich
prev parent reply other threads:[~2016-03-06 22:33 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 ` Re: [lowrisc-dev] " Rich Felker
2016-03-06 22:33 ` Rich Felker [this message]
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=20160306223327.GW9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=lowrisc-dev@lists.lowrisc.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).